From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:52828) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPlqp-0006Wh-O1 for guix-patches@gnu.org; Sun, 12 May 2019 06:37:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hPlqo-0006iD-OI for guix-patches@gnu.org; Sun, 12 May 2019 06:37:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:56606) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hPlqo-0006i4-Kf for guix-patches@gnu.org; Sun, 12 May 2019 06:37:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hPlqo-0002oG-Bp for guix-patches@gnu.org; Sun, 12 May 2019 06:37:02 -0400 Subject: [bug#35697] [PATCH 0/8] Make 'guix system docker-image' readily usable Resent-Message-ID: Received: from eggs.gnu.org ([209.51.188.92]:52533) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPlqf-0006FK-5U for guix-patches@gnu.org; Sun, 12 May 2019 06:36:54 -0400 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Date: Sun, 12 May 2019 12:30:55 +0200 Message-Id: <20190512103055.16832-1-ludo@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: 35697@debbugs.gnu.org Cc: Chris Marusich Hello Guix, On current master, ‘guix system docker-image’ produces an image without an entry point, so one has to carefully follow the “GUIX_NEW_SYSTEM hack” described in the manual. Furthermore, due to other issues, the resulting image doesn’t properly boot because it tries to mount file systems that it cannot mount, such as /dev/shm and /dev/pts. These patches fix both issues, such that one can just do ‘docker create’ and ‘docker start’ to get Guix System up and running in the container. I think that’s a nice improvement. :-) We discussed this Friday on IRC and people said that it’s quite unusual to provide a “full OS” (with PID 1) as a Docker image; instead, people would rather do one image per (micro)service. But anyway, that’s the purpose of ‘guix system docker-image’, and I can imagine it has use cases too. For example, it’s a simple way to get Guix set up in a container, for people who want to perform Guix builds in a container. Thoughts? Ludo’. Ludovic Courtès (8): system: Export 'operating-system-default-essential-services'. linux-container: Improve filtering of unnecessary file systems. services: 'gc-root-service-type' now has a default value. linux-container: Do not add %CONTAINER-FILE-SYSTEMS to Docker image OSes. linux-container: Compute essential services for THIS-OPERATING-SYSTEM. system: Add 'operating-system-with-gc-roots'. docker: 'build-docker-image' accepts an optional #:entry-point. vm: 'system-docker-image' provides an entry point. doc/guix.texi | 18 +++-- gnu/services.scm | 5 +- gnu/system.scm | 18 ++++- gnu/system/linux-container.scm | 30 ++++++--- gnu/system/vm.scm | 18 ++++- gnu/tests/docker.scm | 118 ++++++++++++++++++++++++++++++++- gnu/tests/install.scm | 11 --- guix/docker.scm | 15 +++-- 8 files changed, 195 insertions(+), 38 deletions(-) -- 2.21.0