125 fch@archlinux ~ % podman --log-level debug start archlinux-toolbox :(
INFO[0000] podman filtering at log level debug
DEBU[0000] Called start.PersistentPreRunE(podman --log-level debug start archlinux-toolbox)
DEBU[0000] Ignoring libpod.conf EventsLogger setting "/home/fch/.config/containers/containers.conf". Use "journald" if you want to change this setting and remove libpod.conf files.
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available
WARN[0000] For using systemd, you may need to login using an user session
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1001` (possibly as root)
WARN[0000] Falling back to --cgroup-manager=cgroupfs
DEBU[0000] Using conmon: "/usr/bin/conmon"
DEBU[0000] Initializing boltdb state at /home/fch/.local/share/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver vfs
DEBU[0000] Using graph root /home/fch/.local/share/containers/storage
DEBU[0000] Using run root /run/user/1001/containers
DEBU[0000] Using static dir /home/fch/.local/share/containers/storage/libpod
DEBU[0000] Using tmp dir /run/user/1001/libpod/tmp
DEBU[0000] Using volume path /home/fch/.local/share/containers/storage/volumes
DEBU[0000] Set libpod namespace to ""
DEBU[0000] [graphdriver] trying provided driver "vfs"
DEBU[0000] Initializing event backend file
DEBU[0000] using runtime "/usr/bin/runc"
WARN[0000] Error initializing configured OCI runtime crun: no valid executable found for OCI runtime crun: invalid argument
WARN[0000] Error initializing configured OCI runtime kata: no valid executable found for OCI runtime kata: invalid argument
INFO[0000] Setting parallel job count to 13
DEBU[0000] mounted container "9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77" at "/home/fch/.local/share/containers/storage/vfs/dir/067b06711037140d8dbdf0648b8d364f7d91984e68ce6ba81851dbf30c334b6b"
DEBU[0000] Created root filesystem for container 9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77 at /home/fch/.local/share/containers/storage/vfs/dir/067b06711037140d8dbdf0648b8d364f7d91984e68ce6ba81851dbf30c334b6b
DEBU[0000] /etc/system-fips does not exist on host, not mounting FIPS mode secret
DEBU[0000] set root propagation to "rslave"
DEBU[0000] reading hooks from /usr/share/containers/oci/hooks.d
DEBU[0000] Created OCI spec for container 9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77 at /home/fch/.local/share/containers/storage/vfs-containers/9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77/userdata/config.json
DEBU[0000] /usr/bin/conmon messages will be logged to syslog
DEBU[0000] running conmon: /usr/bin/conmon args="[--api-version 1 -c 9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77 -u 9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77 -r /usr/bin/runc -b /home/fch/.local/share/containers/storage/vfs-containers/9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77/userdata -p /run/user/1001/containers/vfs-containers/9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77/userdata/pidfile -n archlinux-toolbox --exit-dir /run/user/1001/libpod/tmp/exits --socket-dir-path /run/user/1001/libpod/tmp/socket -l k8s-file:/home/fch/.local/share/containers/storage/vfs-containers/9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77/userdata/ctr.log --log-level debug --syslog --conmon-pidfile /run/user/1001/containers/vfs-containers/9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77/userdata/conmon.pid --exit-command /usr/bin/podman --exit-command-arg --root --exit-command-arg /home/fch/.local/share/containers/storage --exit-command-arg --runroot --exit-command-arg /run/user/1001/containers --exit-command-arg --log-level --exit-command-arg error --exit-command-arg --cgroup-manager --exit-command-arg cgroupfs --exit-command-arg --tmpdir --exit-command-arg /run/user/1001/libpod/tmp --exit-command-arg --runtime --exit-command-arg runc --exit-command-arg --storage-driver --exit-command-arg vfs --exit-command-arg --events-backend --exit-command-arg file --exit-command-arg container --exit-command-arg cleanup --exit-command-arg 9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77]"
[conmon:d]: failed to write to /proc/self/oom_score_adj: Permission denied
DEBU[0000] Received: -1
DEBU[0000] Cleaning up container 9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77
DEBU[0000] Network is already cleaned up, skipping...
DEBU[0000] unmounted container "9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77"
Error: unable to start container "9f184fb8090fc071feff34aeb9ba2a10857eef7d913e5370461c3f19b231ec77": time="2020-07-02T20:24:18-03:00" level=warning msg="exit status 1"
time="2020-07-02T20:24:18-03:00" level=warning msg="no directory specified for freezer.state"
time="2020-07-02T20:24:18-03:00" level=warning msg="no directory specified for freezer.state"
time="2020-07-02T20:24:18-03:00" level=error msg="container_linux.go:349: starting container process caused \"process_linux.go:449: container init caused \\\"rootfs_linux.go:46: preparing rootfs caused \\\\\\\"permission denied\\\\\\\"\\\"\""
container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:46: preparing rootfs caused \\\"permission denied\\\"\"": OCI runtime permission denied error