Thanks. I checked ~/.config/containers/storage.conf and it seems the flatpak entry is indeed from that file.

I'm not clear on what is generating that file, but there seems to be no way to alter or remove it reliably:

I don't know what's adding flatpak there, but no matter what I did to remove it, it was added back to the file.

Eventually, I did a chmod 444 on the file to prevent alteration. Now I get this error instead:

```

$ cat ~/.config/containers/storage.conf
[storage]
  driver = "overlay"
  runroot = "/run/user/100900"
  graphroot = "/containers/storage"
  [storage.options]
    mount_program = "/usr/bin/fuse-overlayfs"
$ podman image list
Could not get runtime: error creating runtime static files directory /containers/storage/libpod: mkdir /containers: permission denied

```

Finally, I settled on a modification that I assume ought to work, but unfortunately podman seems to hang:

```

$ cat ~/.config/containers/storage.conf
[storage]
  driver = "overlay"
  runroot = "/run/user/100900"
  graphroot = "~/.config/containers/storage"
  [storage.options]
    mount_program = "/usr/bin/fuse-overlayfs"
$ time podman --log-level debug image list
INFO[0000] running as rootless                          
DEBU[0000] Initializing boltdb state at ~/.config/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver overlay                  
DEBU[0000] Using graph root ~/.config/containers/storage
DEBU[0000] Using run root /run/user/100977              
DEBU[0000] Using static dir ~/.config/containers/storage/libpod
DEBU[0000] Using tmp dir /run/user/100977/libpod/tmp    
DEBU[0000] Set libpod namespace to ""                  
DEBU[0000] [graphdriver] trying provided driver "overlay"
DEBU[0000] overlay: mount_program=/usr/bin/fuse-overlayfs

^C^C^C

real 3m48.563s
user 2m24.923s
sys 1m56.044s

```

Any ideas about what might be abducting my ~/.config/containers/storage.conf (and why), and why podman fails?