Volume cleanup fails
We have - from time to time - a problem where containers are not terminated properly. Best guess is the container was stopped with SIGKILL
after not having terminated with SIGTERM
. After this happened, no new containers/pod can be started:
Dec 30 12:35:04 <HOST> con-<PODNAME>: * #033[36mhugo #033[0mError: error creating container storage: the container name "hugo" is already in use by "<HASH>". You have to remove that container to be able to reuse that name.: that name is already in use
Funny enough, this message repeats for whatever container name you use, with user permissions you have no option to restart.
We should figure out what to cleanup and do this upon pod restarts or add a possibility to run a cleanup of all podman resources.
I found similar problems online: