Previous comment (shm lock manager) was due to a broken system, with /dev/shm not mounted and mode 700. After a reboot, tests pass cleanly. LGTM.

Tests will never pass with the currently-in-use version of podman: https://github.com/containers/podman/issues/10522

(Root cause: container-selinux update broke something that used to work)

@adamwill is there a way to restart/rerun this test? I can't reproduce the failure, and I know that registry.fedoraproject.org has been a source of flakes for some years. When we do 'pull' in our tests, it's often with || (sleep 6;pull again).

see "automated tests" tab.

Specifically, the "update podman" test, eventually drilling down to this log file, which does indeed include a failure regarding registry.fedoraproject.org, although I don't find the string manifest anywhere. @adamwill can you link to the exact log file you're looking at? I have no idea what these tests are, or who wrote them, or how to look at logs, or even how to read those unreadable logs.

FWIW tests pass for me on a 1minutetip f33 VM.

Or maybe it's selinux instead. Sure, can you try rerunning? I'm running tests on my end itm.

I was just looking at those. No, these aren't flakes. I'm pretty sure this is a kernel issue: between the last (successful) run and now, the kernel bumped, and something broke.

To get buildah working, see https://github.com/containers/buildah/issues/3297

Podman LGTM. Buildah, though, is failing a lot of its system tests; and I can't figure out why, and I'm about to give up for the day.

LGTM, aside from some flakes which I've filed issues for.

@lsm5 nothing provides containers-common >= 4:1-21 needed by podman-3:3.3.0-0.20.dev.git599b7d7.fc35.x86_64 (even in updates-testing)

A disturbing number of flakes, but I'm going to ignore them. LGTM.

filtering in podman-remote is broken, filed #10715. Otherwise LGTM

Whew! With new container-selinux, LGTM. Passes podman and podman-remote tests, root and rootless.

With selinux-policy-34.10.1 (now in stable) and a reboot, LGTM.

Never mind: podman run --privileged is still broken even with the above selinux-policy.

Can you include selinux-policy-34.10.1?