You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I build my own Nix Docker image for various things. It's been building successfully for months now, but today, I ran into this issue:
22.67 Error:
22.67 0: Install failure
22.67 1: Error executing action
22.67 2: Action `configure_nix` errored
22.67 3: Action `setup_default_profile` errored
22.67 4: Failed to execute command with status 1 `HOME="/root" NIX_SSL_CERT_FILE="/nix/store/9m6xbd8pcdb6c655b7lifhi5m1igi5rk-nss-cacert-3.101/etc/ssl/certs/ca-bundle.crt" "/nix/store/30gnc15nig1awa11vii9yz3z8518rnr3-nix-2.24.10/bin/nix-env" "--option" "substitute" "false" "-i" "/nix/store/30gnc15nig1awa11vii9yz3z8518rnr3-nix-2.24.10"`, stdout:
22.67 stderr: installing 'nix-2.24.10'
22.67 error:
22.67 … while setting up the build environment
22.67
22.67 error: unable to load seccomp BPF program: Invalid argument
I've had --extra-conf='filter-syscalls = false' per this comment: #955 (comment)
It's been building successfully for months without issue -- however -- today when I attempt to build a multi-arch image -- it's almost like filter-syscalls = false is completely ignored on the foreign architecture.
Here's the steps to reproduce on an x86_64 Linux machine:
I think the issue is that we try to run all the Nix setup commands (like the nix-env command that is erroring) before we drop the Nix configuration... I can't think of a reason we would want to intentionally do that, so we can probably fix this by simply fixing the ordering to run the "place nix.conf" stuff before "run Nix setup commands" stuff.
I've opened #1311 with that trivial fix and set it to upload -- once CI finishes, there are instructions in the PR body for trying it out, if you're so inclined!
EDIT: as of this edit, the binary is ready for testing:
I build my own Nix Docker image for various things. It's been building successfully for months now, but today, I ran into this issue:
I've had
--extra-conf='filter-syscalls = false'
per this comment: #955 (comment)It's been building successfully for months without issue -- however -- today when I attempt to build a multi-arch image -- it's almost like
filter-syscalls = false
is completely ignored on the foreign architecture.However, the same Dockerfile builds normally on the same architecture:
And here's a screenshot of my GitHub Actions running successfully until today 😄
And the failing log output on the ARM64 job -- the AMD64 job on the GitHub Action runner has no issue.
Please let me know if I can provide any more details!
The text was updated successfully, but these errors were encountered: