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
--userns=auto broken after upgrading to kernel 5.19 #1310
Comments
If this is literally So when using idmapped mounts with overlayfs you first want to check that the filesystem used for the lower or upper layers which are supposed to be Idmapped support Idmapped mounts and then whether overlayfs supports being mounted on top of Idmapped layers. Not sure if both checks are currently performed. |
I tested this on a host with ext4 as the rootfs and another host with btrfs as the rootfs. I get the same error in both cases. Could it be something missing in the kernel configuration? |
I've fixed a similar issue some days ago #1309 basically I was using Does the issue you're seeing happen with the first container you create, or do you need at least two? Any chance you could try the patch I've linked above? If that is not enough, there is something else going on when we test for idmapped mounts support. We already have a test in place to verify that idmapped mounts work on top of overlay before using them. |
It happens when I try to start the second container.
Sure, I just built containers/podman@9a83fe3 and bumped #1308 sounds identical to my issue (not sure how I missed it). Thanks for the pointer :) |
Hi
Linux 5.19 added support for
mounting overlay on top of idmapped layers
and support was added with this PR: #1180.After upgrading to 5.19 starting two containers with
--userns=auto
using the same image isn't working anymore (ex: 2xpodman run --rm -t -i --userns=auto archlinux:latest
as root).When trying to start the second container it fails with:
Full debug log for starting the second container:
The same use-case was working without issues on 5.18. I see a
DisableShifting
option in the code, but I'm not sure how to set it, but it could help ruling out #1180 or confirming it is the issue.Tested with both podman 4.1.1 and 4.2.0 on Arch Linux. Kernel 5.18.3-arch1-1 and 5.19.2-arch1-1.
The text was updated successfully, but these errors were encountered: