From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: myglc2@gmail.com, help-guix@gnu.org
Subject: Re: guix package: error: build failed: opening lock file?
Date: Fri, 06 Apr 2018 10:35:16 +0200 [thread overview]
Message-ID: <87r2ns20mz.fsf@gnu.org> (raw)
In-Reply-To: <87bmewc15q.fsf@gmail.com> (Chris Marusich's message of "Thu, 05 Apr 2018 23:13:53 -0700")
Hello,
Chris Marusich <cmmarusich@gmail.com> 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=server17,script=/home/g1/src/vm/qemu-ifup,downscript=/home/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’s a known limitation.
I was thinking we could have the VM talk to the host daemon socket:
guix system vm config.scm --share=/var/guix/daemon-socket
However that doesn’t work, I suppose 9p doesn’t support forwarding
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’.
next prev parent reply other threads:[~2018-04-06 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 19:43 guix package: error: build failed: opening lock file? myglc2
2018-04-06 6:13 ` Chris Marusich
2018-04-06 8:35 ` Ludovic Courtès [this message]
2018-04-06 16:24 ` myglc2
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2ns20mz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cmmarusich@gmail.com \
--cc=help-guix@gnu.org \
--cc=myglc2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).