-
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
1.6 rc2, fc30, rootless: warnings about missing crun #4115
Comments
This repros as rootless, but not as root. I'm really confused as to why default log level is not the same between the two. |
We explicitly set |
Well there's our problem. |
I think it's definitely the re-exec part of rootless. |
Nice. Fixing this bug may then fix #4012 and get gating tests to pass on rawhide. |
@giuseppe Poke - where does rootless re-exec happen? I'm trying to trace the code, but getting lost in the make pause process vs join pause process bit. |
Alright, we seem to be passing literal |
Does not seem directly related to reexec... I can get it to happen both inside and outside the rootless user namespace. |
If we don't do this, we print WARN level messages that we should not be printing by default. Up one WARN message to ERROR so it still shows up by default. Fixes: containers#4115 Fixes: containers#4012 Signed-off-by: Matthew Heon <[email protected]>
(Similar to, but not the same as, #4012)
podman-1.6.0-0.2.rc2.fc30 rootless outputs copious warnings by default:
This is fc30, not fc31. I made the warnings go away by hand-editing
~/.config/containers/libpod.conf
but am concerned that this is going to come back and haunt us; in particular, regular users will end up doing the same (removing runc from config) and then ending up with nonworking podman when they upgrade to fc31.The text was updated successfully, but these errors were encountered: