From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: guix package: error: build failed: opening lock file? Date: Fri, 06 Apr 2018 10:35:16 +0200 Message-ID: <87r2ns20mz.fsf@gnu.org> References: <877eplv3pl.fsf@gmail.com> <87bmewc15q.fsf@gmail.com> 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]:58519) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f4MqC-0005ni-98 for help-guix@gnu.org; Fri, 06 Apr 2018 04:35:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f4Mq8-00055Z-TL for help-guix@gnu.org; Fri, 06 Apr 2018 04:35:24 -0400 Received: from hera.aquilenet.fr ([185.233.100.1]:38286) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1f4Mq8-00052e-GO for help-guix@gnu.org; Fri, 06 Apr 2018 04:35:20 -0400 In-Reply-To: <87bmewc15q.fsf@gmail.com> (Chris Marusich's message of "Thu, 05 Apr 2018 23:13:53 -0700") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Chris Marusich Cc: myglc2@gmail.com, help-guix@gnu.org Hello, Chris Marusich skribis: > myglc2@gmail.com writes: > >> I am running a 'guix system vm' and 'guix package -i' fails ... >> >> g1@server17 ~$ guix package -i icecat >> guix package: error: build failed: opening lock file >> `/gnu/store/4iznqdzql2cp4l2jkr09jn10xxw861c4-mirrors.lock': Read-only >> file system >> >> Any idea what I am doing wrong? Here are the details ... >> >> guix system vm -M 4 -c 4 /home/g1/src/vm/vms/server17/server17.scm >> >> sudo /gnu/store/1vnsn52grzvpzrdndv1f3nkf7mdwd5wk-run-vm.sh -name >> server17 -net >> tap,ifname=3Dserver17,script=3D/home/g1/src/vm/qemu-ifup,downscript=3D/h= ome/g1/src/vm/qemu-ifdn >> -daemonize -display none No need to run that as root. :-) >> TIA - George > > I think this is expected behavior. Yes, it=E2=80=99s a known limitation. I was thinking we could have the VM talk to the host daemon socket: guix system vm config.scm --share=3D/var/guix/daemon-socket However that doesn=E2=80=99t work, I suppose 9p doesn=E2=80=99t support for= warding sockets. The other option would be to make /gnu/store a writable overlayfs, which should allow us to run a local guix-daemon with its own store in the VM. Ludo=E2=80=99.