5:39 a.m.
I'm not a professional, just a user, but maybe I can help.
Am 2024-11-14 08:02, schrieb Matthias Apitz:
1) Why this data remains after stop of container?
Well, you killed the container and didn't kill it gracefully. Podman
doesn't have a central daemon, so who's going to clean it up? In the
same way, firewall and network rules that you haven't mentioned will
remain - no one will clean them up either.
2) Can I just remove this directory with 'rm -r ....'?
Normally yes, but why don't you use `podman container cleanup`?
3) I did a test and renamed such directory to xxxx.away
fb646bf8e1eb6f157c8b2430897df11da78a9e7c0e38858959066d5c40a2adba.away
No error message showed up on next start. Any hits on this?
I believe this is assigned dynamically and controlled via BoltDB or
SQLite. Otherwise start podman with `--log-level debug`
HTH
Tobias