-
Notifications
You must be signed in to change notification settings - Fork 59
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
various issues with podman 4.8 #1625
Labels
Comments
Probably after the first rounds of issues are fixed, we should let it bake in |
Might be interesting to prioritize Fedora gating for podman package updates as it's not the first time it breaks on major releases. |
Totally agree on that. Given to the increased popularity of ostree based systems the |
dustymabe
added a commit
to dustymabe/fedora-coreos-config
that referenced
this issue
Dec 5, 2023
aaradhak
pushed a commit
to aaradhak/fedora-coreos-config
that referenced
this issue
Mar 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are a few issues with podman 4.8 that makes me want to pin it for the upcoming
testing
andnext
releases.$HOME
env var should always include/var/home
, but I think for the silverblue users in the reported issue that wasn't always true or something. Anyway, I can reproduce this issue if I set$HOME
to/home/core
instead of/var/home/core
and run podman and then upgrade to 4.8 so it's probably worth waiting for the fix in 4.8.1.newuidmap
file having the wrong setuid settingspodman exec
containers/podman#20821The text was updated successfully, but these errors were encountered: