On Tue, Jan 3, 2023 at 10:27 AM Daniel Walsh <dwalsh@redhat.com> wrote:

On 12/30/22 08:35, Михаил Иванов wrote:

> You could do a podman system reset and then remove all content
> from the storage with 
> rm -rf  ~/.local/share/containers
> To make sure there is nothing hidden there,

But that's almost exactly what I did:

> I just purged the whole storage using podman system reset.
> I verified that ~/.local/share/containers became empty
> (only bolt database was still remaining using about 200Mb space)

I'm using whatever storage was provided by default podman install
(debian sid/bookworm) podman is 4.3.1 How can I reconfigure it to
different type? I assumed this has to be done in storage.conf but
this file is not present anywhere at all.

I have no idea why debian would be choosing VFS, unless this is an older version of debian and did not support rootless overaly.  You could try installling fuse-overlayfs and doing another reset, then Podman info should show you using overlay with fuse-overlayfs.

Dan,

In Debian, I've chosen to just go with the upstream defaults: https://github.com/containers/storage/blob/8428fad6d0d3c4cded8fd7702af36a09f02b858f/storage.conf#L116-L118

This file is installed verbatim to /usr/share/containers/storage.conf.

Is there a better choice? Does Fedora/Redhat provide a default storage.conf from somewhere else?

Thanks,

-rt

That should be fine.  Fedora goes with that default as well. Does debian support rootless overlay by default?

If not then it would fail over to VFS if fuse-overlayfs is not installed.