I think the host file system is not exposed because podman itself is not working properly: no /etc/subuid and /etc/subguid force us to use sudo. @chax is there anything you can do? Can we use these file in a stateless location?

I think you need to manually create the /etc/subuid and /etc/subgid files. Try $USER:100000:65536

For rationale:

$ cat /etc/login.defs | grep SUB_UID
SUB_UID_MIN                100000
SUB_UID_MAX             600100000
SUB_UID_COUNT               65536
$ cat /etc/login.defs | grep SUB_GID
SUB_GID_MIN                100000
SUB_GID_MAX             600100000
SUB_GID_COUNT               65536

Docs if helpful: https://thomascfoulds.com/2021/01/23/rootless-podman-on-fedora.html

In D13583#232844, @joebonrichie wrote:

I think you need to manually create the /etc/subuid and /etc/subgid files. Try $USER:100000:65536

For rationale:

$ cat /etc/login.defs | grep SUB_UID
SUB_UID_MIN                100000
SUB_UID_MAX             600100000
SUB_UID_COUNT               65536
$ cat /etc/login.defs | grep SUB_GID
SUB_GID_MIN                100000
SUB_GID_MAX             600100000
SUB_GID_COUNT               65536

Yeah, I create them manually for using podman in rootless mode.

Yeah it's required for lxc/lxd as well. I'm hoping that the new kernel feature around id mapping for mounted filesystems will ultimately lead to this no longer being necessary.

In D13583#232844, @joebonrichie wrote:

I think you need to manually create the /etc/subuid and /etc/subgid files. Try $USER:100000:65536

Yes I know that, still on Fedora podman and toolbox work out of the box. I'd be handy to have them ready to use on Solus too.