-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Firecracker exits with 148 when adding vsock. #897
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
Comments
It looks like we forgot to whitelist a system call for the vsock feature. As a temporary workaround you can set the seccomp level to none when starting Firecracker? ./target/x86_64-unknown-linux-musl/debug/firecracker --context='{"id": "fc1", "jailed": false, "seccomp_level": 0, "start_time_us": 0, "start_time_cpu_us": 0} This is a rather dummy context, but it can be adjusted. If you are running with the jailer, you can pass the We will get back with a fix. |
@andreeaflorescu - Awesome, thank you for the temporary fix and the information. |
@xibz does vsock work for you with |
@mcastelino - From what I can tell it works as in I don't get the exit code. However, this isn't with the use of the jailer. I don't think #911 is related to this at least. |
Fixed by #918 |
When seccomp is enabled, several system calls such as sendmsg() and recvmsg() will not be allowed. This is a problem since the vhost-user protocol assumes that we can send some file descriptors out-of-band to other processes running on the same host. Signed-off-by: Sebastien Boeuf <[email protected]>
using
v0.14.0
on Ubuntu 18.04. Get 148 exit code when trying to add vsocks.The text was updated successfully, but these errors were encountered: