-
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
podman buildx - basic test fails under rootless w/ CgroupsV1 #17520
Comments
@giuseppe PTAL, is this expected behavior for CGv1/runc with rootless podman? |
I don't think that depends from cgroupv1 but rather on the storage driver. I'd expect the same output when the graphroot is We should skip the test when Can you please check if it is using vfs? It is not clear from the |
Ahh, you might be onto something there. It's not explicitly called out in the image-build package install list, I'll get a VM and see if it's there or not. |
...well damn, |
Ahh, @giuseppe called it. As the rootless user,
Oddly enough, there is no user or system |
Update: On my Debian VM as root, |
I know absolutely nothing about that problem space, so this is probably not very helpful: I’d go looking for data about how the driver decision was made in At least code inspection suggests log entries like
(but there seem to be no log entries about the logic actually choosing a driver when none is specified, based on the user-provided or built-in priority list — and, worse, if a driver is on the priority list but its initialization fails, that error is AFAICS not logged. At least the latter part seems quite useful for debugging the behavior). |
Sorry @mtrmac I thought this was part of your wheel-house. I appreciate the |
Update:
|
Mystery solved: According to @nalind VFS is the hard-wired default for rootless if nothing else is selected. |
@siretart I'm not sure what the Debian policy / common practice is here. The podman "experience" with the In Fedora there's a
I just verified manually, having this on Debian results in new rootless users getting the |
Ref: containers#17520 Signed-off-by: Chris Evich <[email protected]>
A friendly reminder that this issue had no activity for 30 days. |
To silence my find-obsolete-skips script, remove the '#' from the following issues in skip messages: containers#11784 containers#15013 containers#15025 containers#17433 containers#17436 containers#17456 Also update the messages to reflect the fact that the issues will never be fixed. Also remove ubuntu skips: we no longer test ubuntu. Also remove one buildah skip that is no longer applicable: Fixes: containers#17520 Signed-off-by: Ed Santiago <[email protected]>
Issue Description
Using Debian SID to run podman's integration tests this test is failing because the volume device numbers are (unexpectedly) all
0x801
. Running the test manually viahack/bats
reproduces the same results.Steps to reproduce the issue
Steps to reproduce the issue
hack/get_ci_vm.sh sys podman debian-12 rootless host
)hack/bats 070-build
Describe the results you received
Describe the results you expected
Test should pass
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Debian GNU/Linux bookworm/sid \n \l
Kernel: 6.1.0-4-cloud-amd64
Cgroups: tmpfs
dpkg-query: no packages found matching containers-common
dpkg-query: no packages found matching cri-o-runc
conmon-2.1.6+ds1-1-amd64
containernetworking-plugins-1.1.1+ds1-3+b2-amd64
criu-3.17.1-2-amd64
crun-1.8-1-amd64
golang-2:1.19~1-amd64
libseccomp2-2.5.4-1+b3-amd64
podman-4.3.1+ds1-5+b2-amd64
runc-1.1.4+ds1-1+b2-amd64
skopeo-1.9.3+ds1-1+b1-amd64
slirp4netns-1.2.0-1-amd64
Additional information
Logs from a run in CI showing the same failure & error.
The text was updated successfully, but these errors were encountered: