From: "Ludovic Courtès" <ludo@gnu.org>
To: Zhu Zihao via web <issues.guix.gnu.org@elephly.net>
Cc: 42173@debbugs.gnu.org
Subject: bug#42173: Nix on Guix System: can't update channels
Date: Thu, 16 Jul 2020 12:12:02 +0200 [thread overview]
Message-ID: <877dv37or1.fsf@gnu.org> (raw)
In-Reply-To: <7fc08d8c7780.aa19f4b146749b1@guile.gnu.org> (Zhu Zihao via web's message of "Wed, 15 Jul 2020 07:28:15 +0200")
Hi,
(+Cc: Oleg, who worked on the Nix service.)
Zhu Zihao via web <issues.guix.gnu.org@elephly.net> skribis:
> I found that if I put "sandbox = false" to /etc/nix/nix.conf. Nix can update channel. Maybe nix's sandbox forget to import some guix binary path?
Yes, probably. There’s probably an option similar to the
‘--chroot-directory’ of ‘guix-daemon’ to specify additional directories
that must be in the “sandbox”.
If you find that option, then we can arrange and add all the
dependencies of /gnu/store/…/bin/bash there (similar to what
‘qemu-binfmt-service-type’ does).
However, it’d still be good to find where that /gnu/store/…/bin/bash
file name is captured.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-07-16 10:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 9:56 bug#42173: Nix on Guix System: can't update channels Alexandru-Sergiu Marton
2020-07-13 13:35 ` Ludovic Courtès
2020-07-19 8:14 ` Alexandru-Sergiu Marton
2020-07-15 5:28 ` Zhu Zihao via web
2020-07-16 10:12 ` Ludovic Courtès [this message]
2020-07-21 7:39 ` Oleg Pykhalov
2020-07-21 17:27 ` Oleg Pykhalov
2020-07-22 10:09 ` Ludovic Courtès
2020-07-21 21:28 ` Ludovic Courtès
2020-07-22 6:59 ` bug#42173: [PATCH 1/2] services: base: Export references-file Oleg Pykhalov
2020-07-22 6:59 ` bug#42173: [PATCH 2/2] services: nix: Fix sandbox Oleg Pykhalov
2020-07-22 10:34 ` Ludovic Courtès
2020-07-22 19:38 ` Oleg Pykhalov
2020-07-21 4:05 ` bug#42173: Nix on Guix System: can't update channels Zhu Zihao via web
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=877dv37or1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=42173@debbugs.gnu.org \
--cc=issues.guix.gnu.org@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).