-
Notifications
You must be signed in to change notification settings - Fork 84
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
sandbox fails on debian 10 #161
Comments
cc @giuseppe |
I was also not able to reproduce the error on a fresh installed Debian Buster machine. Could you run slirp4netns under strace, like:
and share the output? It might be that |
Thanks for taking a look!
I have tried with both a tmpfs mounted on /tmp and without that. Currently I have a tmpfs mounted on /tmp. output of
|
thanks for the strace output, it is very helpful. Could you try replacing I think the kernel complains that we don't keep these options set. |
Sadly, that didn't solve the problem.
|
thanks for trying it out. Could you also try to drop the "size=0k" and replace it with NULL? |
Thanks for keeping at it.
To check, I also ran with the original mount options and NULL, but no luck either:
|
could you do just another attempt to replace both "tmpfs" with ""? If you are on Freenode, please poke me (I am |
@rohrschacht Will you open a PR? |
Thanks for reminding me. I wanted to test this setup for some time and everything seems to work fine! I opened a PR now. |
Thanks, let's keep this open until merging #163 |
I compiled podman and slirp4netns from scratch on my debian buster server. When trying to run any container, podman fails with the error:
After that, podman exits with error 126.
I can reproduce this error reliably by following the Usage example from the Readme and adding the
--enable-sandbox
flag at the end of theslirp4netns
command. It gives the same output and exits with error 1.However, I was not able to reproduce it on a fresh debian buster vm, in which I have also compiled podman and slirp4netns from scratch. I retried compiling on my server to no avail. I also tried with the v0.4.1 and v0.4.2 tags from the repo. It is only happening on my server, which seems to suggest it has something to do with my setup.
I already traced down the error to this mount statement in
sandbox.c
.When disabling that code block by commenting it like in this commit, everything works fine. I can run the example and podman also works without error.
Since I don't know how the sandbox works, I don't know why this remount is needed. Would it be ill-advised to run slirp4netns without it?
If so, do you have any suggestions on why that remount fails on my server?
The text was updated successfully, but these errors were encountered: