From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Hinsen Subject: Re: Building Docker images of GuixSD Date: Thu, 9 Nov 2017 09:23:02 +0100 Message-ID: <42c7a184-da30-070d-288c-4b07382e03a6@fastmail.net> References: <87bmldavre.fsf@gmail.com> <87efq8pwrf.fsf@gnu.org> <87mv4viknx.fsf@gmail.com> <87she5kz6i.fsf@gmail.com> <87inez3tnb.fsf_-_@gnu.org> <87tvyg9g5f.fsf@gmail.com> <87o9ogsp9j.fsf@gnu.org> <87y3ngvuyd.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35286) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eCi70-0000nO-DA for guix-devel@gnu.org; Thu, 09 Nov 2017 03:22:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eCi6x-0006k1-7x for guix-devel@gnu.org; Thu, 09 Nov 2017 03:22:58 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:55907) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eCi6w-0006iP-Q7 for guix-devel@gnu.org; Thu, 09 Nov 2017 03:22:55 -0500 In-Reply-To: <87y3ngvuyd.fsf@gmail.com> Content-Language: en-US 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: guix-devel@gnu.org Hi Chris, > I've run GuixSD in a Docker container and returned to tell the tale! Congratulations! And thanks for exploring all this. > Is this helpful? Is it worth polishing up and maintaining? I'm not > entirely sure, and I'd like to know what you think. I think it is useful, mainly for reason 3: > * If you want to run Guix on a system to which Guix hasn't been ported > (like macOS) but your system does run Docker, now you can run Guix on > that system by running it from a GuixSD Docker container. To which I might add a less obvious one: with GuixSD nicely integrated into the Docker universe, it has a better chance of adoption by people committed to Docker, and thus a better chance of becoming a/the preferred way of constructing Docker images. In other words, an attempt to take over the (Docker) world from inside. > For the third bullet point, I don't know of any other reasonable way to > get Guix working in Docker (although one could certainly run Guix in a > VM using a technology other than Docker, such as QEMU). To run Guix, I have been trying this approach for a while, but I am still much further away from running Guix on my Mac than you are. First, QEMU: forget it on the Mac. It's not nearly as advanced/stable as it is under Linux. You can run Guix with QEMU under macOS, but it's slow and crashes a bit too often to rely on it. I moved on to VirtualBox, which runs a basic GuixSD without any major problem. But what you get is an isolated virtual machine. I haven't yet found a usable strategy for accessing the macOS file system from GuixSD. VirtualBox relies on its proprietary guest OS add-ins. I suspect they could be ported to GuixSD from a technical point of view, but it's not a trivial job and you'd have to remove the term "free software" from your brain for a while to do it. Currently I am trying NFS, exporting my Mac home directory via an NFS server on the Mac (easy) and mounting it from GuixSD (no success so far, because of the very incomplete NFS support in GuixSD). I expect this will work eventually, but in terms of performance it will probably never get to what you can achieve with Docker. Konrad.