-
Notifications
You must be signed in to change notification settings - Fork 83
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] podman run fails due to slirp4netns on Tinycore 11.1 #249
Comments
Seems to be related to running on a rootfs (and thus not having any access to pivot_root) ? containers/podman#8846 (comment) So some kind of Tiny Core Linux runs everything straight from the initrd (RAM disk), by default |
I have the same error in an alpine image where I want to run buildah/podman I can start a container in the alpine build container in privileged mode with the following command
and the container is starting with no error and I can work with it.
followed by the error
|
And if i do the manual steps described here https://github.com/rootless-containers/slirp4netns#usage and add --enable-sandbox in the start command
the same error occurs
Without the --enable-sandbox everything work like described. pod is calling slirp4netns in the following way
|
I found the problem... the build container ist started with docker and the default seccomp.json file which is missing pivot_root! https://github.com/moby/moby/blob/master/profiles/seccomp/default.json I copied the content of the file and added pivot_root to the syscalls! After that the build container has to be run with --security-opt=./seccomp.json and the the error with --enable-sandbox is gone (except the followed error with chown which i don't investigated till now) |
Description
podman run
fails on tinycore 11.1 VM because of some issue related toslirp4netns
. Using slirp4netns version 1.1.8.Steps to reproduce the issue:
Install podman on tinycore using manual install
Run
podman run hello-world
Results
The text was updated successfully, but these errors were encountered: