After stop of a container massive data remains below
~/.local/share/containers/storage/overlay

Steps to reproduce:

cups@srap57dxr1:~> podman image list
REPOSITORY                      TAG         IMAGE ID      CREATED       SIZE
localhost/sles15-sp6-v73-sp1    latest      caeabd52aa4a  46 hours ago  26 GB
localhost/sles15-sp6-v73        latest      690f90eaed0f  46 hours ago  20.2 GB
registry.suse.com/bci/bci-base  15.6        075e3ce8c342  11 days ago   125 MB

cups@srap57dxr1:~> podman run --tz='Europe/Berlin' -d -p 2022:22 sles15-sp6-v73

cups@srap57dxr1:~> podman container list

CONTAINER ID  IMAGE                                COMMAND     CREATED         STATUS         PORTS                                                                                            NAMES
43e7d4f12f27  localhost/sles15-sp6-v73:latest                  10 minutes ago  Up 10 minutes  0.0.0.0:2022->22/tcp  gracious_sinoussi

This start creates two new dirs below /home/cups/.local/share/containers/storage/overlay:


srap57dxr1:/home/cups/.local/share/containers/storage/overlay # ls -ltr | tail -2
drwxr-xr-x 2 cups root 17408 Nov 13 11:14 l
drwx------ 6 cups root  1024 Nov 13 11:14 fb646bf8e1eb6f157c8b2430897df11da78a9e7c0e38858959066d5c40a2adba

srap57dxr1:/home/cups/.local/share/containers/storage/overlay # du -sh fb646bf8e1eb6f157c8b2430897df11da78a9e7c0e38858959066d5c40a2adba
5.4G    fb646bf8e1eb6f157c8b2430897df11da78a9e7c0e38858959066d5c40a2adba

Now I kill the container with:

cups@srap57dxr1:~> podman kill 43e7d4f12f27
43e7d4f12f27

The dirs remain:

srap57dxr1:/home/cups/.local/share/containers/storage/overlay # ls -ltr | tail -2
drwxr-xr-x 2 cups root 17408 Nov 13 11:14 l
drwx------ 5 cups root  1024 Nov 13 11:27 fb646bf8e1eb6f157c8b2430897df11da78a9e7c0e38858959066d5c40a2adba

and occupy ~5.4G space:

srap57dxr1:/home/cups/.local/share/containers/storage/overlay # du -sh fb646bf8e1eb6f157c8b2430897df11da78a9e7c0e38858959066d5c40a2adba
5.4G    fb646bf8e1eb6f157c8b2430897df11da78a9e7c0e38858959066d5c40a2adba

and this on any start/stop of the container.

I did a closer look what is there below such a directory. We use such
containers to test the update of our server software to the next
release. Such update brings ~1 GByte gzip'ed packages and files and below
such a directory is exactly what was updated, binary identical with what
was stored as new versions of the files, for example a new delivered
file '/opt/lib/sisis/etc/pos.rc' is there as
fb646bf8e1eb6f157c8b2430897df11da78a9e7c0e38858959066d5c40a2adba/diff/opt/lib/sisis/etc/pos.rc
like many other files:

# find fb646bf8e1eb6f157c8b2430897df11da78a9e7c0e38858959066d5c40a2adba | grep /opt/lib/sisis | wc -l
2494

# find fb646bf8e1eb6f157c8b2430897df11da78a9e7c0e38858959066d5c40a2adba | grep /usr/local/sisis-pap | wc -l
27879


Questions:

1) Why this data remains after stop of container?

2) Can I just remove this directory with 'rm -r ....'?

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?

Thanks

--
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.
_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io