From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35057) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1etawC-0001WA-NN for guix-patches@gnu.org; Wed, 07 Mar 2018 10:25:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1etawA-0006Fj-3a for guix-patches@gnu.org; Wed, 07 Mar 2018 10:25:04 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:41785) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1etaw9-0006FZ-Vh for guix-patches@gnu.org; Wed, 07 Mar 2018 10:25:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1etaw9-0000bn-Pl for guix-patches@gnu.org; Wed, 07 Mar 2018 10:25:01 -0500 Subject: [bug#30572] [PATCH 4/7] docker: Allow the use of a custom temporary directory. Resent-Message-ID: From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) References: <20180222103528.5108-1-cmmarusich@gmail.com> <20180222103528.5108-4-cmmarusich@gmail.com> <20180226014859.4f7fe37c@scratchpost.org> <87po4rra78.fsf@garuda.local.i-did-not-set--mail-host-address--so-tickle-me> <20180227004658.4cefda82@scratchpost.org> <87y3jfvy7k.fsf@gmail.com> <87r2p6z7td.fsf@gnu.org> <87k1uoiesh.fsf@gmail.com> Date: Wed, 07 Mar 2018 16:24:30 +0100 In-Reply-To: <87k1uoiesh.fsf@gmail.com> (Chris Marusich's message of "Wed, 07 Mar 2018 07:24:30 +0100") Message-ID: <876067syc1.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: Chris Marusich Cc: 30572@debbugs.gnu.org Hello, Chris Marusich skribis: > Another option here would be to build the Docker image without using a > VM in the first place. Perhaps we can use namespaces, but I haven't > tried that yet, since the VM approach worked. I tried without a VM > first, and I quickly found that I couldn't do many things in a normal > derivation that I needed to do in order to build the image (e.g., create > device files). I don't know if I can do all those necessary things > without using a VM. We need a VM so that we can be root and create and mount file systems, right? That=E2=80=99s a good reason to use a VM. :-) What about making /tmp in the VM a 9p mount of /tmp outside the VM? That way this would be transparent, and no need to fiddle with the VM disk sizes. WDYT? Thanks, Ludo=E2=80=99.