unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: stuebinm <stuebinm@disroot.org>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: guix system docker-image: nix not found
Date: Sun, 9 May 2021 21:59:06 +0200	[thread overview]
Message-ID: <e97c7e29-444a-26e0-88c4-106bd709639b@disroot.org> (raw)
In-Reply-To: <YJg8I03qhW4imtJs@jasmine.lan>


[-- Attachment #1.1: Type: text/plain, Size: 1035 bytes --]

> On Sun, May 09, 2021 at 08:58:59PM +0200, stuebinm wrote:
>> When trying with dummy values (taken from my own system config),
>> `guix system docker-image system.scm` fails to build the
>> guix-docker-image.tar.gz.drv, and the build log contains
>>
>>    /gnu/store/...bash-5.0.16/bin/bash: nix: command not found
> 
> It would help if you sent the entire log file as an attachment.

nevermind; I thought that /was/ the entire logfile, but it turns out 
that I had the emacs nix-mode installed, which recognised the logfile as 
a derivation and tried to call nix to parse it, and apparently its 
failure mode (since I don't have nix installed) was to write its own 
stderr into the buffer without giving any indication that wasn't the 
real content of the file …

The actual logfile is of the vm running out of memory, which is a known 
issue [1]; I'll look into how to solve that.

Sorry for the unnecessary message, but thanks anyways for responding :)

~stuebinm

[1] https://issues.guix.gnu.org/48178


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2021-05-09 23:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-09 18:58 guix system docker-image: nix not found stuebinm
2021-05-09 19:46 ` Leo Famulari
2021-05-09 19:59   ` stuebinm [this message]
2021-05-09 20:38     ` Leo Famulari

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=e97c7e29-444a-26e0-88c4-106bd709639b@disroot.org \
    --to=stuebinm@disroot.org \
    --cc=help-guix@gnu.org \
    --cc=leo@famulari.name \
    /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).