Rootful podman using --uidmap fails after container update

[tschan]

Starting the following container works as expected:

sudo podman run -it --rm '--uidmap=0:1000:1' '--uidmap=1:100000:65536' docker.io/library/caddy:2.10.0@sha256:133b5eb7ef9d42e34756ba206b06d84f4e3eb308044e268e182c2747083f09de

Running the same with the updated container:

sudo podman run -it --rm '--uidmap=0:1000:1' '--uidmap=1:100000:65536' docker.io/library/caddy:2.10.2@sha256:4163a5c7b7631707956db4057720ec75de429992d5e3aa518d54872c01644dbe

Results in this error:

Error: mounting storage for container 1c0abebdb6118f86a4d178944f4ba333d7105122719ccb0a89c0af8c82a58072: creating overlay mount to /var/lib/containers/storage/overlay/e3a090dab6a4fc5f68b9153237852188a31de82a4049b805c1895fd6a7d6b1e9/merged, mount_data="lowerdir=/var/lib/containers/storage/overlay/e3a090dab6a4fc5f68b9153237852188a31de82a4049b805c1895fd6a7d6b1e9/mapped/0/l/A7XNUOIJHABHMAFBZ3ZZP76AYH:/var/lib/containers/storage/overlay/e3a090dab6a4fc5f68b9153237852188a31de82a4049b805c1895fd6a7d6b1e9/mapped/0/l/DP7F3ONLAKN3OJ4MVK62TTODEA:/var/lib/containers/storage/overlay/e3a090dab6a4fc5f68b9153237852188a31de82a4049b805c1895fd6a7d6b1e9/mapped/0/l/LXKFN4D3V6NQNNNOSEBA2LKH6Y:/var/lib/containers/storage/overlay/e3a090dab6a4fc5f68b9153237852188a31de82a4049b805c1895fd6a7d6b1e9/mapped/0/l/CQ3M3ZCXKAVW2BGHX5NC6CPXNR:/var/lib/containers/storage/overlay/e3a090dab6a4fc5f68b9153237852188a31de82a4049b805c1895fd6a7d6b1e9/mapped/0/l/diff1:/var/lib/containers/storage/overlay/e3a090dab6a4fc5f68b9153237852188a31de82a4049b805c1895fd6a7d6b1e9/mapped/0/l/33YXPHS5NB7X7WEJD7L4OJNEDA,upperdir=/var/lib/containers/storage/overlay/e3a090dab6a4fc5f68b9153237852188a31de82a4049b805c1895fd6a7d6b1e9/diff,workdir=/var/lib/containers/storage/overlay/e3a090dab6a4fc5f68b9153237852188a31de82a4049b805c1895fd6a7d6b1e9/work,volatile": no such file or directory

Any idea what changed in the container to break this?

$ podman version
Client:       Podman Engine
Version:      5.6.0
API Version:  5.6.0
Go Version:   go1.24.6
Built:        Tue Jan  1 01:00:00 1980
OS/Arch:      linux/amd64

[tschan]

"Fixed" it by doing a podman system reset. No idea how it got in a state where this was necessary though.