-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error: unable to load seccomp BPF program: Invalid argument #324
Comments
That's pretty interesting. It seems you have some non-default seccomp configurations? What OS is this on? What version of docker? |
aarch64-darwin (macos Ventura 13.2.1 with m1 CPU) |
Thanks! I might have to try to set up a reproduction as I've not seen something like this before. |
There are some ideas here NixOS/nix#2651 (and more google search results) |
It seems a workaround might be to disable syscall filtering in Nix itself. I'd imagine the way Docker containerizes things, filtering syscalls might not be within the container-based sandbox and wouldn't work with the default installer either. Maybe add |
That works, except autodetection seems to not work now and user has to add some args manually. Not sure this is something you want to tackle or is intended.
|
My colleague @lucperkins was able to reproduce this today on their machine, we're investigating more. |
Investigating more: Without a In
In
With a In
In
|
This is because x86_64 containers on ARM Macs run inside Some possible workarounds:
Note that |
We discussed making the installer detect if we are inside a runtime situation like this and add a line to the configured I'm wondering if it is possible to offer users a unified Docker/Podman config as a result. #373 shows it is kind of a mess. |
## Description: Fix the cross platform docker images that are trying to install nix by replacing the installer and passing extra config params. ## Is this change user facing? NO ## References (if applicable): - DeterminateSystems/nix-installer#324 - NixOS/nix#5258
The text was updated successfully, but these errors were encountered: