From: Ian Denhardt <ian@zenhack.net>
To: David Thompson <dthompson2@worcester.edu>, guix-devel@gnu.org
Subject: Re: Containers on Guix
Date: Sat, 22 Nov 2014 11:51:27 -0500 [thread overview]
Message-ID: <20141122165126.19565.59657@vulcan.local.tld> (raw)
In-Reply-To: <87lhn6eh12.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
Quoting David Thompson (2014-11-19 21:34:49)
> I did some reading about how Docker creates containers and discovered
> that it uses systemd-nspawn[0] to do it. Since Guix uses dmd, using
> systemd-nspawn isn't an option. Does anyone have thoughts on how we
> might have similar functionality in the Guix distro?
I'm not so sure that docker actually needs systemd -- the docker
documentation has instructions for a number of systems that don't use
systemd. A quick scan suggests they're using lxc, at least on some
systems.
> Would an nspawn equivalent be appropriate for dmd? Or a completely
> separate program? This seems to be a Linux only feature, so if we added
> a container creation program, would it make it harder to support the
> Hurd?
I'm sure there are other things already packaged that don't really have
any hope of working on top of another kernel. This is going to be hard
to do portably, but I don't think it's worth worrying about too much
yet. Probably some work will have to happen upstream on the Hurd
project.
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAABAgAGBQJUcL8OAAoJEPZUuMfUyjy48kQP/0eNkJ8x9qGKbsGSqATV0E5f
FtJBY38+CUpulsI1HpZxUiKGej1UtM+8O8if5ajQAibtpg0oMnalkhT4yaBjloaU
i74AIM+nhBEmSOW/5LfeJggK5RSrrISwaomOTcN8XHPA4xrl2EpE2Z4B7PtJiqlO
jGkCg8bkoI0nn8heV6JZejqhzjWUWRsp2HJZE/tb7KsMohK6TvzP2FtHysvsjrU0
CCNSijlGu9Fuai7cQ9SCvVRz4tS1ZNYit//3DTQATEjsqc2zSFy7GLhw4V/3uVVH
fMSq/JpCnbUdj4DR+00uQ7OMSL8CieX4CHmEC/4uVtv9wtmw5RA1lgF6EZSTsiGv
XBRBYG2XCzrMKUfW1FRfIICLd7U2ctBVSyOG3nkUZA6VK2rFWQwFFtOr17z4mctq
X4YW7fQwxd2BYve/8z0FVOGsg5e5CIZsAF68uVQrKPqh+VB8eMe24PFDTeIEtRCh
yvGRCgWQ3UHM+NW6POU0rXgNyq53TI1RV5sqls90SN7378mM+grk5m42TwTEB+t/
YqLq9xRLteZ2td5Nf2vsUd433ZtQxi//Fd49NiT1gni0Rabjf8Vc76v64a9PC5XI
tTn9AZEzpg2loUDxBWuSUzNo4WPt7+dHJ8QKDSm82I2Nnd4gwwj23uPiCLL8oCFB
Q9Y2pOLoGHq/L4UdSo+I
=a2a7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-11-22 16:51 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
2014-11-20 14:51 ` Ludovic Courtès
2014-11-22 16:51 ` Ian Denhardt [this message]
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=20141122165126.19565.59657@vulcan.local.tld \
--to=ian@zenhack.net \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
/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.