From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>,
"Ludovic Courtès" <ludovic.courtes@inria.fr>
Subject: Re: Docker and singularity containers
Date: Tue, 15 Jan 2019 13:31:39 +0100 [thread overview]
Message-ID: <CAJ3okZ1NOd+eJ0fcQ6mujnP756M34NhtkSmyf83AaibM76ov+w@mail.gmail.com> (raw)
In-Reply-To: <87pntbrsig.fsf@elephly.net>
Dear Ricardo,
> I don’t know. We could have one with R + all CRAN and bioconductor
> packages that we currently offer.
Ok, it seems a good start.
> > - how?
>
> That’s easier: with “guix pack”. We would create a Cuirass job to build
> a pack regularly. We’d need to add support for hooks to publish the
> generated pack on DockerHub, though we could just as well host them
> ourselves.
Aside the DockerHub issue, ok.
And let fix the DockerHub ethical issue later. :-)
I mean let start by build Docker images with Cuirass, then we will see
how/where to publish them.
Just to fix the idea, the simple Docker image containing
Emacs+Guile+Geiser (the scheme SDK ;-) is about 300MB with '.tar.gz'
and 1GB with only '.tar'
>
> Would you like to give this a try? A good first step is to list the
> steps that need to be performed. A first implementation might even be
> done with a cron job. I could add this to berlin.guixsd.org when you’re
> ready.
I am giving a try.
Thank you.
All the best,
simon
next prev parent reply other threads:[~2019-01-15 12:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 15:16 Docker and singularity containers Pjotr Prins
2018-09-12 17:35 ` Ludovic Courtès
2018-09-12 17:43 ` Ricardo Wurmus
2018-09-12 18:30 ` Pjotr Prins
2018-09-12 20:59 ` Ricardo Wurmus
2018-09-13 6:10 ` Pjotr Prins
2018-09-13 7:21 ` Ricardo Wurmus
2019-01-04 18:57 ` zimoun
2019-01-05 16:14 ` Ricardo Wurmus
2019-01-06 3:10 ` Mike Gerwitz
2019-01-06 12:09 ` zimoun
2019-01-08 9:07 ` swedebugia
2019-01-08 9:10 ` swedebugia
2019-01-15 12:31 ` zimoun [this message]
2018-09-13 6:53 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ1NOd+eJ0fcQ6mujnP756M34NhtkSmyf83AaibM76ov+w@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.