From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org, 宋文武 <iyzsong@gmail.com>
Subject: Re: Containers on Guix
Date: Fri, 21 Nov 2014 10:16:48 +0100 [thread overview]
Message-ID: <87bno0ap6n.fsf@gnu.org> (raw)
In-Reply-To: <87mw7lb3dl.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> (David Thompson's message of "Thu, 20 Nov 2014 23:10:14 -0500")
David Thompson <dthompson2@worcester.edu> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>>> A container is programs or full os running in an isolated environment.
>>> For a full container with rootfs, we can:
>>> build the rootfs:
>>> of Guix: by using a form of `guix system init'
>>
>> I think it’s enough and cheaper to build the system (as per ‘guix system
>> build’) and to bind-mount its closure in the container’s file system.
>
> I'm having trouble with this approach. pflask tries to create a /proc
> directory but can't because that would be writing to the store.
Hmm, the store should be under /container/gnu/store, not /container, no?
> Do I need to bind-mount each sub-directory within the
> /gnu/store/...-system directory so that the root of the container
> directory is still writable?
Let’s say /container is the root of the container. It must be a
regular, writable directory.
As a first step it’s OK to bind-mount all of /gnu/store to
/container/gnu/store.
What guix-daemon does is to bind-mount precisely each element of the
store that is needed, so there’s no “leak”.
HTH!
Ludo’.
next prev parent reply other threads:[~2014-11-21 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 2:34 Containers on Guix David Thompson
2014-11-20 2:36 ` David Thompson
2014-11-20 13:30 ` 宋文武
2014-11-20 14:08 ` Thompson, David
2014-11-20 20:49 ` Ludovic Courtès
2014-11-20 21:24 ` Thompson, David
2014-11-21 4:10 ` David Thompson
2014-11-21 9:16 ` Ludovic Courtès [this message]
2014-11-20 14:51 ` Ludovic Courtès
2014-11-22 16:51 ` Ian Denhardt
2014-11-22 17:31 ` 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=87bno0ap6n.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
--cc=iyzsong@gmail.com \
/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.