Unable to run podman rootfull / rootless inside chroot environment. #18392
-
Heyo, I'm having a problem with podman inside privileged chroot. Every time I'm trying to use it, I'm getting:
> podman run --name builder -it alpine
Resolved "alpine" as an alias (/etc/containers/registries.conf.d/00-shortnames.conf)
Trying to pull docker.io/library/alpine:latest...
Getting image source signatures
Copying blob f56be85fc22e done
Error: copying system image from manifest list: writing blob: adding layer with blob "sha256:f56be85fc22e46face30e2c3de3f7fe7c15f8fd7c4e5add29d7f64b87abdaa09": processing tar file(remount /, flags: 0x44000: invalid argument): exit status 1
> podman run --name builder -it alpine
cannot clone: Operation not permitted
Error: cannot re-exec process I've installed inside chroot Is there any way to make podman work inside chroot? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
There are probably syscalls and other components that are being blocked within a chroot. You could attempt to see what syscalls are being blocked using strace. Why do you want to run podman within a chroot? @giuseppe Ideas? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
These both show up as empty files/ |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
After switching on > podman pull alpine
Resolved "alpine" as an alias (/etc/containers/registries.conf.d/00-shortnames.conf)
Trying to pull docker.io/library/alpine:latest...
Getting image source signatures
Copying blob f56be85fc22e done
ERRO[0020] While applying layer: ApplyLayer stdout: stderr: remount /, flags: 0x44000: invalid argument exit status 1
Error: copying system image from manifest list: writing blob: adding layer with blob "sha256:f56be85fc22e46face30e2c3de3f7fe7c15f8fd7c4e5add29d7f64b87abdaa09": ApplyLayer stdout: stderr: remount /, flags: 0x44000: invalid argument exit status 1 Full strace log: strace_root_vfs.txt |
Beta Was this translation helpful? Give feedback.
creating a user namespace is blocked in a chroot, here is the relevant check in the kernel:
so it is not a Podman issue, and nothing we can do about it