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: Fri, 4 Jan 2019 19:57:32 +0100 [thread overview]
Message-ID: <CAJ3okZ3DYZrY=OzC7WkUgxVKw8LA_1ZyB7g3Rur-Z_E3rLzEcQ@mail.gmail.com> (raw)
In-Reply-To: <87a7olkgln.fsf@elephly.net>
Dear,
I am interested by Docker images for specific tasks (scientific
python, R.sumo, etc.).
Around me, people are pulling a debian Docker image then feed it with
some specific dockerfile to produce a R environment ready to use.
And I trying to do that for some bioconductor packages about Flow
Cytometry data analysis.
Well, why not push to DockerHub time to time.
I agree that will attract people if Guix provide an official docker
image reachable from DockerHub.
For example, there is an official image of neuroscience Debian packages:
https://hub.docker.com/_/neurodebian
When searching about Guix, it is not so meaningful:
https://hub.docker.com/search?q=guix&type=image
Therefore:
- which tasks and which packages?
- how?
even if the how is already discussed.
Could we discuss that at the before-FOSDEM days.
What do you think?
All the best,
simon
next prev parent reply other threads:[~2019-01-04 18:57 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 [this message]
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
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='CAJ3okZ3DYZrY=OzC7WkUgxVKw8LA_1ZyB7g3Rur-Z_E3rLzEcQ@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.