podman: New buildah/timeout/external container flakes

New weird flakes seen in buildah treadmill. I’m filing all under one issue, but they might be unrelated:

not ok 119 podman ps --external
...
# podman build -t thiswillneverexist -
STEP 1/3: FROM quay.io/libpod/testimage:20221018
STEP 2/3: RUN touch /intermediate.image.to.be.pruned
--> 0c116d0cdcf9
STEP 3/3: RUN sleep 30
timeout: sending signal TERM to command '/var/tmp/go/src/github.com/containers/podman/bin/podman'
[ rc=124 (expected) ]
#/vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
#|     FAIL: podman build did not get killed within 10 seconds
#| expected: -le 10
#|   actual:     32

(ISTR something changing in buildah signal handling recently)

And:

not ok 248 podman diff with buildah container 
...
$ podman images --all --format {{.Repository}}:{{.Tag}} {{.ID}}
quay.io/libpod/testimage:20221018 f5a99120db64
buildahctr
$ podman diff --format json buildahctr
Error: buildahctr not found: layer not known

And:

not ok 137 podman rm container from storage
...
$ podman container exists --external testimage-working-container
[ rc=1 (** EXPECTED 0 **) ]

All of these are buildah-related. I haven’t seen them in any other PRs, but this has been the lightest PR week in memory. If we don’t see these in regular podman CI, it might be something in the new buildah vendoring.

• debian-12 : sys podman debian-12 root host boltdb
  • 05-19 09:06 in [sys] podman ps --external
• debian-12 : sys podman debian-12 rootless host boltdb
  • 05-19 09:05 in [sys] podman rm container from storage
  • 05-19 09:05 in [sys] podman diff with buildah container
• rawhide : sys podman rawhide rootless host sqlite
  • 05-19 09:09 in [sys] podman ps --external