Rootless podman play kube
fails to start a Pod when using custom podman build
#22903
Closed
mgoltzsche
started this conversation in
General
Replies: 1 comment 4 replies
-
Likely a bug in podman, I cannot see where we actually create the so I guess you could just run |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am maintaining an alternative alpine-based podman container image. When I tried to upgrade it from v4 to v5.1.1 here my e2e test case that runs the
podman play kube
command as unprivileged user 1000 within a docker container failed. Specifically it fails to mount/tmp/storage-run-1000/containers/networks/rootless-netns/run
into the containers at/run
because the directory/tmp/storage-run-1000/containers/networks/rootless-netns
does not exist. The parent directory does exist, though. Thepodman play kube
test case is the only one failing. All other tests succeed.I am not reporting this as a podman bug since the test scenario works with the official podman image
quay.io/podman/stable:v5.0.3
, indicating that the problem is caused by my build.Here's how to reproduce the problem:
docker build -t local-podman .
play kube
command within the container (with apod.yaml
file mounted):I also ran the command with
--log-level=debug
but it didn't clarify the root cause for me:Debug log
Debug log
Here's the `podman info` output.
podman info
Running the test using the minimal version of the image that uses
crun
instead ofrunc
and that has the samecontainers.conf
as the official podman container results in the same problem.Since this works with the official podman container I wonder what am I missing within my custom container image?
Any hint would be appreciated!
Beta Was this translation helpful? Give feedback.
All reactions