From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: Re: guix package: error: build failed: opening lock file? Date: Thu, 05 Apr 2018 23:13:53 -0700 Message-ID: <87bmewc15q.fsf@gmail.com> References: <877eplv3pl.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52581) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f4KdP-0002o1-Qd for help-guix@gnu.org; Fri, 06 Apr 2018 02:14:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f4KdM-0007Jk-Ld for help-guix@gnu.org; Fri, 06 Apr 2018 02:14:03 -0400 Received: from mail-io0-x22b.google.com ([2607:f8b0:4001:c06::22b]:43397) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f4KdM-0007JL-Fs for help-guix@gnu.org; Fri, 06 Apr 2018 02:14:00 -0400 Received: by mail-io0-x22b.google.com with SMTP id q84so390538iod.10 for ; Thu, 05 Apr 2018 23:14:00 -0700 (PDT) In-Reply-To: <877eplv3pl.fsf@gmail.com> (myglc2@gmail.com's message of "Thu, 05 Apr 2018 15:43:50 -0400") 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: myglc2@gmail.com Cc: help-guix@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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/ho= me/g1/src/vm/qemu-ifdn > -daemonize -display none > > TIA - George I think this is expected behavior. The script produced by the "guix system vm" command maps the host's store into the guest. This happens in system-qemu-image/shared-store-script (defined in gnu/system/vm.scm), if you are curious. I suspect the the intent is to prevent the undesirable situation in which two Guix daemons (the one in your host and the one in your guest VM) attempt to manage the same store. Bad things could happen in that situation. For example, one daemon might garbage collect some paths that were still valid from the other daemon's perspective. The store is only intended to be managed by a single daemon, which is probably why the store is mounted read-only in the guest. The same is true for the "guix system container" command, also. Currently, if you need a read-write store in a VM, the easiest solution is probably to use "guix system vm-image" or "guix system disk-image". =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlrHECEACgkQ3UCaFdgi Rp0QGA//XEGWZqHUl0xUrVVEZnBu3gBNgDVukr4nXO1wmkDRNMfYc0d/FjgvHqXt pBomRwIUcwsMemdT1ox1QmnVoY4VtfliAH6lH75y9pC6myqKwn8aKM1QgTVq1vZr PSjrpvy9yv6AGe3HtKXVaVN3dzE1EIVvx7B0ohkH6n24jFwtxo23IPcy8ds4bBG6 +BCIXSOfmD5sU0Z08tdISl+CvepZkf3WtFaPW1yYHU6M5aZVp+xzLqOBGeKYKPsf q0yKIo4+qlQDCiCvNzKBhpTllTNWPBdIy0hIPxcepHByS3jtj8yxWwKVIsPtXsTb uaYdrCyKfk68kEV/5dQ/oIabjTb66OzaCVY8JjKz46+88ZmAcD9B2XaHWQ5RRIa1 L21zAXbfE2zTVelO5K5xbnICzlu9G+IoBztGo7dCEaWkuLBjoykG2qSAE6lVIjaE qkTVn1KqJbuwbjI9gD6ZWvZbSlT3GPEeNtqa1KueLaOO48DKn5PZyNVRH7IN299l qBqtnuDp1oSU8sfrgLzQchxv7XI+RAP+qYEUoFW7zIHbcjM/NZP6b82wKFQlikv1 4A7E5lpdxttpGFg4jOFF6oNR4jeWpIOzOOwaCTt25dtBBbISEAtCQvv9F+AhE/2q ft69SyZJjWuRCbsUBT8y9bxolAzGD1ffKbdKK12ObUWhdsMYQSM= =NY19 -----END PGP SIGNATURE----- --=-=-=--