From: Cloudef <Cloudef@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] nix: do not disable sandbox by default
Date: Thu, 17 Feb 2022 17:58:09 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35666@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
New issue by Cloudef on void-packages repository
https://github.com/void-linux/void-packages/issues/35666
Description:
### System
* xuname: Void 5.12.14_1 x86_64-musl AuthenticAMD uptodate rFFFF
* package: nix-2.3.12_1
### Expected behavior
/etc/nix.conf should have sandbox on, and should build packages as expected in such isolated environment.
### Actual behavior
/etc/nix.conf has sandbox turned off by default, and it fails unexpectedly when turned on due to a misconfiguration with sandbox-paths. Nix mounts `/bin/sh` into the sandboxed namespace, but this binary is linked against musl libc and thus fails to work in such a sandboxed environment.
The workaround is to install busybox-static and edit sandbox-paths in /etc/nix.conf so that /bin/sh points to busybox.static instead.
### Steps to reproduce the behavior
1. Install nix and make sure sandboxing is turned on (restart daemon)
2. Use the following default.nix
```nix
{ pkgs ? import <nixpkgs> {} }:
pkgs.buildPackages.rustPlatform.buildRustPackage rec {
pname = "diesel-cli-ext";
version = "0.3.6";
cargoSha256 = "1npmr1sy7d6gv7j3r8c03c7k7c9fv0kvipl96cm6g1c90qqba2hx";
src = pkgs.fetchCrate {
inherit version;
crateName = "diesel_cli_ext";
sha256 = "0zf98kydxgb9mc77x7r4d0vmkfzgi5h4h6n1dhpgq2if9ybyci0b";
};
}
```
3. build will fail with misleading error:
```
tar (child): gzip: Cannot exec: No such file or directory
tar (child): Error is not recoverable: exiting now
```
4. strace reveals the tar actually does `/bin/sh -c gzip`
next reply other threads:[~2022-02-17 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 16:58 Cloudef [this message]
2022-02-17 16:58 ` Cloudef
2022-06-24 2:16 ` github-actions
2022-06-24 5:11 ` Cloudef
2022-09-24 2:14 ` github-actions
2022-09-24 6:33 ` Cloudef
2022-12-25 1:58 ` github-actions
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35666@inbox.vuxu.org \
--to=cloudef@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).