From: ludo@gnu.org (Ludovic Courtès)
To: Amirouche Boubekki <amirouche.boubekki@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>, help-guix@gnu.org
Subject: Re: Help understand some guix concepts
Date: Tue, 09 Jan 2018 13:41:52 +0100 [thread overview]
Message-ID: <87fu7ftd9r.fsf@gnu.org> (raw)
In-Reply-To: <CAL7_Mo-6ML1Uj6Dzz0s2uW+n0ctNJmTPZb9y3WoJ9=AJ7OfLCQ@mail.gmail.com> (Amirouche Boubekki's message of "Mon, 01 Jan 2018 21:39:35 +0000")
Hi,
Sorry for the late reply.
Amirouche Boubekki <amirouche.boubekki@gmail.com> skribis:
> *Q:* Does chroot guix/sd use chroot?
The build daemon, ‘guix-daemon’, uses chroot (among other tools) to
perform isolated builds:
https://www.gnu.org/software/guix/manual/html_node/Invoking-guix_002ddaemon.html
> *Q:* Do guix developers use chroot somehow?
[...]
> *Q:* Do guix developers use 'guix system init' in combination with chroot?
They could, but it’s not very useful or convenient. ‘guix system vm’ or
‘guix system container’ (the latter actually uses chroot(2)) are simpler
interfaces.
> *Q: *Does guix/sd use cgroups <https://en.wikipedia.org/wiki/Cgroups>?
No (not yet).
> *Q: *Does guix/sd containers enforce an image format?
No.
Docker & co. often associate “container” and “image format” because what
they deal with are binary images.
Conversely Guix and GuixSD have a detailed view of package composition,
service composition, etc. Thus, they can spawn a container that
contains everything you specified (see ‘guix system container’ and ‘guix
environment -C’), and they can also create binary images that contain
everything you want (see ‘guix pack’ and ‘guix system vm-image’).
However, neither Guix nor GuixSD is in the business of running software
from containers in the format defined by Docker & co.
> *Q: *Can guix/sd use images? What are the advantages?
> *Q: *How does networking happens in guix/sd?
> *Q: *Is it possible to bind multiple interfaces via a bridge on the host
> system to the container?
Not easily so.
> *Q: *Is it possible or recommended to run shepherd inside a guix container?
‘guix system container’ runs GuixSD in a container, and GuixSD uses the
Shepherd.
> *Q:* isn't AppImage <https://en.wikipedia.org/wiki/AppImage> a
> "combination" of 'guix pack' and 'guix container'.
AppImage is a *format* for distributing software, as Wikipedia notes.
‘guix pack’ is a tool to create images (“binary images”, “bundles”,
depending on the preferred terminology). See
<https://www.gnu.org/software/guix/blog/2017/creating-bundles-with-guix-pack/>.
> *Q: *Is it possible to have Xorg running inside a container and then use
> ssh -X to access it? Is there a way to avoid the ssh -X?
In theory we should be able to run Xorg in a ‘guix system container’,
but it would have to use a display different from that of the host.
Never tried though.
That said, you don’t need a running X server on the remote host to use
“ssh -X”.
HTH,
Ludo’.
prev parent reply other threads:[~2018-01-09 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL7_Mo9+T40hD_z-8=dSRecOHgzhHezzgLwM_2Y097oXiBxfbQ@mail.gmail.com>
2018-01-01 21:39 ` Help understand some guix concepts Amirouche Boubekki
2018-01-09 12:41 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fu7ftd9r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=amirouche.boubekki@gmail.com \
--cc=guix-devel@gnu.org \
--cc=help-guix@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).