Weired error message after reboot: Error: current system boot ID differs from cached boot ID

[groovyman]

Dear friends,

i am running a Fedora F40 Server in order to run my apps, where some of them use podman to run rootless container.
In order to archive this, i created some technical users, that acts like domains, that run in turn some container apps.

One of these technical users shows a strange behaviour after some updates. Whenever i reboot my sever and i login
on my technical user i get the following message, whenever i call podman:

podman ps
Error: current system boot ID differs from cached boot ID; an unhandled reboot has occurred. Please delete directories "/run/user/1002/containers" and "/Home/techlxoffice/rteDataSpace/podmanTMP" and re-run Podman

Then i go into the podmanTMP directory and i see a couple of files:

$ ls -l /Home/techlxoffice/rteDataSpace/podmanTMP
insgesamt 4
-rw-r--r--. 1 techlxoffice techlxoffice  37  3. Jul 21:55 alive
-rw-r--r--. 1 techlxoffice techlxoffice   0  3. Jul 21:55 alive.lck
drwxr-x---. 1 techlxoffice techlxoffice   0  4. Jul 01:26 exits
drwxr-x---. 1 techlxoffice techlxoffice 128  3. Jul 21:55 persist
drwx------. 1 techlxoffice techlxoffice   0  3. Jul 21:55 rp

So when i remove all these files, podman is running, and the systemd --user is also able to run the application, that normally lauch up, when the host is starting.

Do you have an idea, what went wrong. This configuration suddently fails, maybe due to a update, that took place a week ago.

[Luap99]

https://github.com/containers/podman/releases/tag/v5.1.0

Podman now detects unhandled system reboots and advises the user on proper mitigations.

In general the podman tmpdir and rundir must be on a tmpfs or deleted on boot in order to allow for podman to function properly

[groovyman]

Salut @Luap99

so the best strategy is to ignore the --tmpdir argument, when building the image and let podman decide to choose the correct default tmp-directory for this step.

Would that be the right conclusion from your answer?

Thank you for your help!

[Luap99]

you can use --tmpdir but you should make sure that this directory is on a tmpfs or deleted on boot before you launch podman.