Closed paulcalabro closed 3 months ago
if this is rhel, why not file an official support issue? there is some preference for this over using upstream github for these kinds of things.
@baude Well, we filed one for our issue. MSFT support tried to close the issue before it could reach Red Hat support. It's still an open issue. (Update: Same situation like @paulcalabro described. For our case, the support engineer did not identify the root cause so far.)
@baude We did, however, the support engineer we worked with was unable to identity the root cause of the issue. We're still trying to figure it out.
A friendly reminder that this issue had no activity for 30 days.
We only support the latest version upstream, so either try to reproduce with the latest upstream version and/or try to get your support ticket escalated if this is big problem for you.
Issue Description
After upgrading Podman from v4.4.1 to v4.6.1, I am no longer able to run rootless containers.
Steps to reproduce the issue
Steps to reproduce the issue
podman run alpine:3.19.1
(I've also tried other images)Describe the results you received
This is the error message:
Describe the results you expected
I expected the container to run successfully like it had done in previous releases.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
SELinux is in permissive mode atm:
User storage configuration:
User container configuration:
Additional information
netns
tohost
userns
tohost
Can trigger the failure also by creating a new network and using that: