El día jueves, noviembre 14, 2024 a las 11:39:24 +0100, Tobias Wendorff escribió:
I'm not a professional, just a user, but maybe I can help.
Thanks in any case for reading and your hints.
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.
I kill the container because 'stop' does not work either: cups@srap57dxr1:~> podman stop zealous_blackburn WARN[0010] StopSignal SIGQUIT failed to stop container zealous_blackburn in 10 seconds, resorting to SIGKILL zealous_blackburn
2) Can I just remove this directory with 'rm -r ....'?
Normally yes, but why don't you use `podman container cleanup`?
I used this like: cups@srap57dxr1:~> podman container cleanup zealous_blackburn zealous_blackburn but the data below .local/share/containers/storage/overlay remain.
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`
Will try this. Thanks matthias -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub Annalena Baerbock: "We are fighting a war against Russia ..." (25.1.2023) I, Matthias, I am not at war with Russia. Я не воюю с Россией. Ich bin nicht im Krieg mit Russland.