1. error joining network namespace for container

If you restart windows without stopping the container first, there is a great probability that this problem will occur

 

Solution:

Stop the stopped container before starting the exited container You will be prompted that you cannot start, but now you can podman PS or continue to execute podman start to start the container. It’s amazing, isn’t it

podman stop $(podman ps 2>&1 | grep -oE 'for container [a-f0-9]+' | awk '$0=$NF')
podman start $(podman ps --format '{{.Names}}' --filter status=exited)

2. Error refreshing volume

Something like this

$ podman ps -a
ERRO[0000] Error refreshing volume 20115fd77826acd6308a6dceb6318062fcdae8e3626c7b3367de25d328e93a2f: error acquiring lock 1 for volume 20115fd77826acd6308a6dceb6318062fcdae8e3626c7b3367de25d328e93a2f: file exists
ERRO[0000] Error refreshing volume 74d3b3f07e31ce9baabd307ebfea62c0860aa2454babff744c04e828eb571b89: error acquiring lock 2 for volume 74d3b3f07e31ce9baabd307ebfea62c0860aa2454babff744c04e828eb571b89: file exists
ERRO[0000] Error refreshing volume fbbb149df2df1ed1ac1092976de6216e604ea773958ee812e3e24e0d1e635850: error acquiring lock 1 for volume fbbb149df2df1ed1ac1092976de6216e604ea773958ee812e3e24e0d1e635850: file exists
ERRO[0000] Error refreshing volume spec: error acquiring lock 1 for volume spec: file exists
CONTAINER ID  IMAGE   COMMAND  CREATED  STATUS  PORTS   NAMES

Solution

podman system renumber