Works great! LGTM! =)

Works

There's one test failure which isn't the usual ones:

not ok 315 podman pod create - hashtag AllTheOptions
# (from function `die' in file ./helpers.bash, line 700,
#  from function `run_podman' in file ./helpers.bash, line 381,
#  in test file ./200-pod.bats, line 258)
#   `run_podman run --rm --pod mypod $IMAGE ip link show' failed
# [02:00:30.068153106] # /usr/bin/podman-remote rm -t 0 --all --force --ignore
# [02:00:30.101596763] # /usr/bin/podman-remote ps --all --external --format {{.ID}} {{.Names}}
# [02:00:30.135100772] # /usr/bin/podman-remote images --all --format {{.Repository}}:{{.Tag}} {{.ID}}
# [02:00:30.168736753] quay.io/libpod/testimage:20221018 f5a99120db64
# [02:00:30.299236706] # /usr/bin/podman-remote build -t infra_ll3c8vj4pr -
# [02:00:31.194487001] STEP 1/3: FROM quay.io/libpod/testimage:20221018
# STEP 2/3: RUN ln /home/podman/pause /pause_3ycEISmcIU
# --> fae11d1edd71
# STEP 3/3: ENTRYPOINT ["/original-entrypoint-should-be-overridden"]
# COMMIT infra_ll3c8vj4pr
# --> daeef4175991
# Successfully tagged localhost/infra_ll3c8vj4pr:latest
# daeef41759911ba25bfe44242459d8bfd2ee69bc016566295eafd99589b9b36f
# [02:00:31.202150487] # /usr/bin/podman-remote pod create --name=mypod --pod-id-file=/tmp/podman_bats.DEC6nJ/pod-id-file --mac-address=B2:F5:7B:E5:58:13 --hostname=gz2iir79qi.v496dq4kri.net --add-host qwhwp9jegg.xr06et47wr.xyz:172.20.129.84 --dns 172.20.244.151 --dns-search pod98wd7gh3citk.abc --dns-option ndots:39 --publish 6275:5835 --label 5jrSYagB48R=LOTvbgO7LxAjPCV4eAzEvn --infra-image infra_ll3c8vj4pr --infra-command /pause_3ycEISmcIU --infra-name infra_container_i3h1tr61sb
# [02:00:31.289250245] c42c610b405f58ce1bf6edd9d38f6085987a38d7c02e8e1618bc99d70f915dbd
# [02:00:31.296002870] # /usr/bin/podman-remote pod inspect --format {{(index .Containers 0).ID}} mypod
# [02:00:31.328359492] d6167d833b2470b3b071098e46308711ccbb3f679d25b5677bd871874fbf948c
# [02:00:31.333136962] # /usr/bin/podman-remote container inspect --format {{.Config.Entrypoint}} d6167d833b2470b3b071098e46308711ccbb3f679d25b5677bd871874fbf948c
# [02:00:31.369008895] /pause_3ycEISmcIU
# [02:00:31.375236487] # /usr/bin/podman-remote container inspect --format {{.Name}} d6167d833b2470b3b071098e46308711ccbb3f679d25b5677bd871874fbf948c
# [02:00:31.407810365] infra_container_i3h1tr61sb
# [02:00:31.414151230] # /usr/bin/podman-remote run --rm --pod mypod quay.io/libpod/testimage:20221018 ip link show
# [02:00:31.784546156] time="2023-08-11T02:00:31Z" level=error msg="Removing container f9b5b0cd75d6681ae7bbe164b9fe2fa89f4f55f84c5fd4ac84d81f356e7af604: cleaning up container f9b5b0cd75d6681ae7bbe164b9fe2fa89f4f55f84c5fd4ac84d81f356e7af604: unmounting container f9b5b0cd75d6681ae7bbe164b9fe2fa89f4f55f84c5fd4ac84d81f356e7af604 storage: cleaning up container f9b5b0cd75d6681ae7bbe164b9fe2fa89f4f55f84c5fd4ac84d81f356e7af604 storage: unmounting container f9b5b0cd75d6681ae7bbe164b9fe2fa89f4f55f84c5fd4ac84d81f356e7af604 root filesystem: unmounting \"/var/lib/containers/storage/overlay/a483bf8755c0450df532570041e2194dd9e4afc556e182a7f296d4c088aa9d7d/merged\": invalid argument"
# Error: preparing container f9b5b0cd75d6681ae7bbe164b9fe2fa89f4f55f84c5fd4ac84d81f356e7af604 for attach: crun: executable file `ip` not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not found
# [02:00:31.787867262] [ rc=127 (** EXPECTED 0 **) ]
# #/vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
# #| FAIL: exit code is 127; expected 0
# #\^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# [02:00:31.793011010] # /usr/bin/podman-remote pod rm -f -t 0 -a
# [02:00:32.017057469] Error: not all containers could be removed from pod c42c610b405f58ce1bf6edd9d38f6085987a38d7c02e8e1618bc99d70f915dbd: removing pod containers. 1 error occurred:
#   * cleaning up container d6167d833b2470b3b071098e46308711ccbb3f679d25b5677bd871874fbf948c: unmounting container d6167d833b2470b3b071098e46308711ccbb3f679d25b5677bd871874fbf948c storage: cleaning up container d6167d833b2470b3b071098e46308711ccbb3f679d25b5677bd871874fbf948c storage: unmounting container d6167d833b2470b3b071098e46308711ccbb3f679d25b5677bd871874fbf948c root filesystem: unmounting "/var/lib/containers/storage/overlay/ae3a0ff6d9cde6b119892bc16a3bb2154ebdecad4a19e45406e5b17bbc6dd16d/merged": invalid argument
# [02:00:32.019113847] [ rc=125 (** EXPECTED 0 **) ]
# #/vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
# #| FAIL: exit code is 125; expected 0
# #\^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# [02:00:32.021023970] # /usr/bin/podman-remote rm -f -t 0 -a
# [02:00:32.153102830] # /usr/bin/podman-remote rmi --ignore localhost/podman-pause:4.6.1-1691705273
# # [teardown]
# [02:00:32.181791028] # /usr/bin/podman-remote pod rm -t 0 --all --force --ignore
# [02:00:32.230333241] c42c610b405f58ce1bf6edd9d38f6085987a38d7c02e8e1618bc99d70f915dbd
# [02:00:32.232206824] # /usr/bin/podman-remote rm -t 0 --all --force --ignore
# [02:00:32.260823481] # /usr/bin/podman-remote network prune --force
# [02:00:32.289595031] # /usr/bin/podman-remote volume rm -a -f
# setup(): removing stray external container d6167d833b24 (infra_container_i3h1tr61sb)
# [setup] # podman rm -f d6167d833b24
# Error: removing storage for container "d6167d833b24": unmounting "/var/lib/containers/storage/overlay/ae3a0ff6d9cde6b119892bc16a3bb2154ebdecad4a19e45406e5b17bbc6dd16d/merged": invalid argument
# setup(): removing stray external container f9b5b0cd75d6 (hopeful_meninsky)
# [setup] # podman rm -f f9b5b0cd75d6
# Error: removing storage for container "f9b5b0cd75d6": unmounting "/var/lib/containers/storage/overlay/a483bf8755c0450df532570041e2194dd9e4afc556e182a7f296d4c088aa9d7d/merged": invalid argument
# setup(): removing stray image localhost/infra_ll3c8vj4pr:latest
# setup(): removing stray image daeef4175991
# setup(): removing stray image <none>:<none>
# setup(): removing stray image fae11d1edd71

shall we just restart the tests? @santiago

One of our nastiest flakes. It should pass on rerun, but I'm concerned that it failed in both f37 and f38. Normally this has a one-in-ten-runs flake rate.

well, the tests are run in four permutations for each update - root/rootless, and root/rootless cgroupsv2 - so it's not so unusual that a 1/10 flake would happen on at least one of those runs.

FWIW I can list and start my containers

OK, only known failures this time (SELinux and pasta), waiving.

Containers runing ok here