-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Rootless podman in rootless podman container fails with inconsistent messages #20812
Comments
Try: We need to fix these Warnings about the /run/secrets directory. |
Also can you do |
Do you mean to try these for the first podman, or that podman-in-podman invocation? |
First podman, Kernel does not allow a processes to modify a modified /proc. |
The behaviour, including the nondeterminism, seems to still be there:
|
In a possibly related issue, I'm seeing similar warning messages running quay.io/buildah/stable on my CRI-O kubernetes cluster:
|
Yes we need to figure out how to fix this on systems that do not have subscption-manager installed on them, Probably drop the Warning to info. |
quay.io/buildah/stable and quay.io/podman/stable images now forward the mounts.conf subscriptions into their containers but if the host is not using subscription manager these pass throughs warn about missing files, which is not useful to the user. fixes: containers/podman#20812 Signed-off-by: Daniel J Walsh <[email protected]>
quay.io/buildah/stable and quay.io/podman/stable images now forward the mounts.conf subscriptions into their containers but if the host is not using subscription manager these pass throughs warn about missing files, which is not useful to the user. fixes: containers/podman#20812 Signed-off-by: Daniel J Walsh <[email protected]>
This issue however was about that
vs.
not about those mountpoint |
"no logs from conmon" is #10927, one of our longest-standing and most annoying flakes. I've never seen it on |
quay.io/buildah/stable and quay.io/podman/stable images now forward the mounts.conf subscriptions into their containers but if the host is not using subscription manager these pass throughs warn about missing files, which is not useful to the user. fixes: containers/podman#20812 Signed-off-by: Daniel J Walsh <[email protected]>
Issue Description
I try to debug some rootless setups in OpenShift per https://www.redhat.com/sysadmin/podman-inside-kubernetes. I know it says
and I try to find out what exactly would fail, to possibly amend the SELinux / OpenShift policies. So it is expected that my attempt to run a rootless podman container in a rootless container fails.
However, the error message I get when running a rootless container in a rootless container seem not stable which is worrying.
Steps to reproduce the issue
Steps to reproduce the issue
$ podman run --rm -ti --user podman quay.io/podman/stable
[podman@8c2d1ecef2c7 /]$ podman run --rm -ti --user podman quay.io/podman/stable
[podman@8c2d1ecef2c7 /]$ podman run --rm -ti --user podman quay.io/podman/stable
Describe the results you received
Describe the results you expected
I expect the error message to be the same every time.
podman info output
On the host:
In the container:
The text was updated successfully, but these errors were encountered: