all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludovic.courtes@inria.fr (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Docker and singularity containers
Date: Wed, 12 Sep 2018 19:35:07 +0200	[thread overview]
Message-ID: <878t4662lw.fsf@gnu.org> (raw)
In-Reply-To: <20180912151616.iwt3kqb77zd76wf6@thebird.nl> (Pjotr Prins's message of "Wed, 12 Sep 2018 17:16:16 +0200")

Hello,

Pjotr Prins <pjotr.public12@thebird.nl> skribis:

> I know this is not a priority right now for maintainers, but I think
> it would be really useful if we provide ready-made containers for
> certain packages. This will allow people who have the infrastructure
> to run containers to start using reproducible Guix builds. With that,
> I think there will be an increased interest in our technology.

FWIW at work people a colleague of mine got into Guix with the goal of
being able to run their software on a different cluster that has
Singularity but not Guix.

People interested in this might use Guix on their laptop just to build
Singularity images and view it as a tool to build bundles (which is of
course unsatisfactory but it’s a way to get started!).

> Maybe it is something to discuss at FOSDEM, but I wonder what it would
> take to have the build farm automatically provide Docker containers
> for marked packages and offer them through the web interface.

A while back we fantasized about the possibility of having a web service
that would produce “packs” of Guix packages on demand.  That may allow
us to be #1 on HN for a couple of hours ;-), but it would also be quite
resource-hungry (and the service itself needs to be written to begin
with.)  Such a service would have to use its own resources IMO, not
those of the build farm, which is already busy enough.

Ludo’.

  reply	other threads:[~2018-09-12 17:35 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 [this message]
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
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=878t4662lw.fsf@gnu.org \
    --to=ludovic.courtes@inria.fr \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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.