From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Help understand some guix concepts Date: Tue, 09 Jan 2018 13:41:52 +0100 Message-ID: <87fu7ftd9r.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59065) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eYtE7-0005VC-SP for guix-devel@gnu.org; Tue, 09 Jan 2018 07:42:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eYtE3-0004Yu-Tc for guix-devel@gnu.org; Tue, 09 Jan 2018 07:41:59 -0500 In-Reply-To: (Amirouche Boubekki's message of "Mon, 01 Jan 2018 21:39:35 +0000") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Amirouche Boubekki Cc: guix-devel , help-guix@gnu.org Hi, Sorry for the late reply. Amirouche Boubekki skribis: > *Q:* Does chroot guix/sd use chroot? The build daemon, =E2=80=98guix-daemon=E2=80=99, uses chroot (among other t= ools) to perform isolated builds: https://www.gnu.org/software/guix/manual/html_node/Invoking-guix_002ddaem= on.html > *Q:* Do guix developers use chroot somehow? [...] > *Q:* Do guix developers use 'guix system init' in combination with chroot? They could, but it=E2=80=99s not very useful or convenient. =E2=80=98guix = system vm=E2=80=99 or =E2=80=98guix system container=E2=80=99 (the latter actually uses chroot(2)= ) are simpler interfaces. > *Q: *Does guix/sd use cgroups ? No (not yet). > *Q: *Does guix/sd containers enforce an image format? No. Docker & co. often associate =E2=80=9Ccontainer=E2=80=9D and =E2=80=9Cimage= format=E2=80=9D 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 =E2=80=98guix system container=E2=80= =99 and =E2=80=98guix environment -C=E2=80=99), and they can also create binary images that conta= in everything you want (see =E2=80=98guix pack=E2=80=99 and =E2=80=98guix syst= em vm-image=E2=80=99). 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 containe= r? =E2=80=98guix system container=E2=80=99 runs GuixSD in a container, and Gui= xSD uses the Shepherd. > *Q:* isn't AppImage a > "combination" of 'guix pack' and 'guix container'. AppImage is a *format* for distributing software, as Wikipedia notes. =E2=80=98guix pack=E2=80=99 is a tool to create images (=E2=80=9Cbinary ima= ges=E2=80=9D, =E2=80=9Cbundles=E2=80=9D, depending on the preferred terminology). See . > *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 =E2=80=98guix system container= =E2=80=99, but it would have to use a display different from that of the host. Never tried though. That said, you don=E2=80=99t need a running X server on the remote host to = use =E2=80=9Cssh -X=E2=80=9D. HTH, Ludo=E2=80=99.