http://bugzilla.opensuse.org/show_bug.cgi?id=1137059 http://bugzilla.opensuse.org/show_bug.cgi?id=1137059#c1 José Guilherme Vanz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |jguilhermevanz@suse.com --- Comment #1 from José Guilherme Vanz --- I can simulate the issue: vanz@germ130:~> podman images ERRO[0000] No subuid ranges found for user "vanz" in /etc/subuid vanz@germ130:~> cat /etc/os-release NAME="openSUSE Leap" VERSION="15.1 " ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.1" PRETTY_NAME="openSUSE Leap 15.1" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.1" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" vanz@germ130:~> -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1137059 http://bugzilla.opensuse.org/show_bug.cgi?id=1137059#c3 --- Comment #3 from José Guilherme Vanz --- I just saw in the podman manual: Rootless mode Podman can also be used as non-root user. When podman runs in rootless mode, a user namespace is automatically created for the user, defined in /etc/subuid and /etc/subgid. Containers created by a non-root user are not visible to other users and are not seen or managed by podman running as root. It is required to have multiple uids/gids set for an user. Be sure the user is present in the files /etc/subuid and /etc/subgid. If you have a recent version of usermod, you can execute the following commands to add the ranges to the files $ sudo usermod --add-subuids 10000-75535 USERNAME $ sudo usermod --add-subgids 10000-75535 USERNAME Or just add the content manually. $ echo USERNAME:10000:65536 >> /etc/subuid $ echo USERNAME:10000:65536 >> /etc/subgid See the subuid(5) and subgid(5) man pages for more information. Images are pulled under XDG_DATA_HOME when specified, otherwise in the home directory of the user under .local/share/containers/storage. Currently the slirp4netns package is required to be installed to create a network device, otherwise rootless containers need to run in the network namespace of the host. @tbechtold, ignore my question from comment 2. The answer is in the bug title. I think the manual documentation resolve the bug, don't you think? -- You are receiving this mail because: You are on the CC list for the bug.