all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: guix-devel@gnu.org, Joshua Marshall <j.marshall@arroyo.io>
Subject: Re: Declarative containers
Date: Wed, 27 Mar 2019 12:18:02 +0100	[thread overview]
Message-ID: <87sgv8efbp.fsf@gnu.org> (raw)
In-Reply-To: <87zhphwbju.fsf@roquette.mug.biscuolo.net> (Giovanni Biscuolo's message of "Tue, 26 Mar 2019 22:49:57 +0100")

Hi,

Giovanni Biscuolo <g@xelera.eu> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:

[...]

>> We could have a ‘container’ (or ‘sub-system’?) service;
>
> mumble: `container` is so abused that it's starting to become a buzzword
> to my ears, `sub-system` is probably more semantic

The Hurd has had this thing called “sub-Hurd”, which is similar to what
we’re talking about.

>> you’d pass it an <operating-system> and it’d create a Shepherd service
>> that runs that OS in a container.
>
> what is the method used to instantiate containers with Guix?

‘guix system container’ creates an executable that starts the container.
That executable is a Guile program that uses (gnu build
linux-container), a module that provides facilities to create processes
under separate name spaces, etc.

IOW all the functionality is provided by Guix; no systemd-nspawn,
bubblewrap, lxc, etc.

Ludo’.

      reply	other threads:[~2019-03-27 11:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 17:47 Feature requests Joshua Marshall
2019-03-22 22:30 ` Julien Lepiller
2019-03-23 14:01   ` Joshua Marshall
2019-03-23 14:36     ` Julien Lepiller
2019-03-25  9:40 ` Giovanni Biscuolo
2019-03-25 17:38   ` Joshua Marshall
2019-03-26 17:19   ` Declarative containers Ludovic Courtès
2019-03-26 21:49     ` Giovanni Biscuolo
2019-03-27 11:18       ` Ludovic Courtès [this message]

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=87sgv8efbp.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=g@xelera.eu \
    --cc=guix-devel@gnu.org \
    --cc=j.marshall@arroyo.io \
    /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.