From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thompson, David" Subject: Re: Containers on Guix Date: Thu, 20 Nov 2014 16:24:53 -0500 Message-ID: References: <87lhn6eh12.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> <87d28irocj.fsf@gmail.com> <87tx1tvbqw.fsf@gnu.org> 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]:34591) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XrZDp-0006SY-IL for guix-devel@gnu.org; Thu, 20 Nov 2014 16:25:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XrZDj-0005R7-H6 for guix-devel@gnu.org; Thu, 20 Nov 2014 16:25:01 -0500 Received: from na3sys009aog105.obsmtp.com ([74.125.149.75]:41115) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XrZDj-0005Qf-8m for guix-devel@gnu.org; Thu, 20 Nov 2014 16:24:55 -0500 Received: by mail-pa0-f41.google.com with SMTP id rd3so3380695pab.0 for ; Thu, 20 Nov 2014 13:24:53 -0800 (PST) In-Reply-To: <87tx1tvbqw.fsf@gnu.org> 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= Cc: guix-devel , =?UTF-8?B?5a6L5paH5q2m?= On Thu, Nov 20, 2014 at 3:49 PM, Ludovic Court=C3=A8s wrote: > =E5=AE=8B=E6=96=87=E6=AD=A6 skribis: > >> I think what we need is pflask: https://github.com/ghedo/pflask > > Indeed, that seems like a good fit! The concern I have is something the author brings up in the README: "Compared to LXC, pflask is easier to use since it doesn't require any pre-configuration (all the options can be passed via the command-line). pflask is mostly intended for testing, building and experimenting, whereas LXC is a more complete solution, better suited for production environments." I want something that can handle production environments. But it's a good starting point anyway. Using an improved version of the guix-daemon to do this might still be the best long term solution. >> 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=E2=80=99s enough and cheaper to build the system (as per =E2= =80=98guix system > build=E2=80=99) and to bind-mount its closure in the container=E2=80=99s = file system. Didn't know about the 'build' subcommand. I will try that out. Thanks! - Dave