Looks like this is a known bug that was recently fixed. As far as not wiping your existing containers, I’m not sure. If you can get back to a version of podman that worked then you could possibly export them to files and then re-import them after the upgrade.
Ah, thank you very much! I thought it had something to do with silverblue and so I did not look into the podman issues.
The odd thing is that I am running podman 0.10.1.3 and as reported the issue seems to only affect 0.11.*. I guess I will just wait for the next upgrade and then I will see if things are fixed.
I just noticed that fedora-toolbox uses a volume mount --volume /run/user/1000:/run/user/1000 and so it could mean that this somehow breaks the database.