From: ludo@gnu.org (Ludovic Courtès)
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: help-guix@gnu.org
Subject: Re: container issues
Date: Fri, 01 Jan 2016 16:01:02 +0100 [thread overview]
Message-ID: <87twmxl4y9.fsf@gnu.org> (raw)
In-Reply-To: <568526EE.5090002@uq.edu.au> (Ben Woodcroft's message of "Thu, 31 Dec 2015 23:00:30 +1000")
Ben Woodcroft <b.woodcroft@uq.edu.au> skribis:
> $ ./pre-inst-env guix environment --ad-hoc -C ruby
It works for me on GuixSD.
> In execvp of fsck.none: No such file or directory
> 'fsck.none' exited with code 127 on /home/ben/git/guix; spawning REPL
This comes from ‘mount-file-system’ in (gnu build file-systems), called
from (gnu build linux-container).
I suspect an ABI issue if you haven’t rebuilt since be21979d
(Dec. 22nd.)
Could you run ‘make clean-go && make’ and then retry?
TIA, and happy GNU year!
Ludo’.
next prev parent reply other threads:[~2016-01-01 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 13:00 container issues Ben Woodcroft
2015-12-31 14:59 ` Thompson, David
2015-12-31 23:58 ` Ben Woodcroft
2016-01-01 18:11 ` Ludovic Courtès
2016-01-01 15:01 ` Ludovic Courtès [this message]
2016-01-02 0:10 ` Ben Woodcroft
2016-01-03 11:28 ` Ludovic Courtès
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=87twmxl4y9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=b.woodcroft@uq.edu.au \
--cc=help-guix@gnu.org \
/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).