/kind bug
Description
It's a fresh installment on my home computer.
Funnily enough I did not experience this on my server machines, which also run Manjaro OS.
rootless podman info
$ podman info
Error: cannot setup namespace using newuidmap: exit status 1
subuid
$ cat /etc/subuid
folaht:10000:65536
subgid
$ cat /etc/subgid
folaht:10000:65536
Steps to reproduce the issue:
-
pacman -S podman
-
podman info
Output of podman version:
$ sudo podman version
Version: 3.4.0
API Version: 3.4.0
Go Version: go1.17.1
Git Commit: 6e8de00bb224f9931d7402648f0177e7357ed079
Built: Fri Oct 1 12:14:18 2021
OS/Arch: linux/amd64
Output of podman info --debug:
$ sudo podman info --debug
host:
arch: amd64
buildahVersion: 1.23.1
cgroupControllers:
- memory
- pids
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: /usr/bin/conmon appartient à conmon 1:2.0.30-1
path: /usr/bin/conmon
version: 'conmon version 2.0.30, commit: 2792c16f4436f1887a7070d9ad99d9c29742f38a'
cpus: 4
distribution:
distribution: manjaro
version: unknown
eventLogger: journald
hostname: pjehrsohmehj
idMappings:
gidmap: null
uidmap: null
kernel: 5.4.150-1-MANJARO
linkmode: dynamic
logDriver: journald
memFree: 18123808768
memTotal: 37484195840
ociRuntime:
name: crun
package: /usr/bin/crun appartient à crun 1.2-1
path: /usr/bin/crun
version: |-
crun version 1.2
commit: 4f6c8e0583c679bfee6a899c05ac6b916022561b
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
os: linux
remoteSocket:
exists: true
path: /run/podman/podman.sock
security:
apparmorEnabled: true
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: false
seccompEnabled: true
seccompProfilePath: /etc/containers/seccomp.json
selinuxEnabled: false
serviceIsRemote: false
slirp4netns:
executable: /usr/bin/slirp4netns
package: /usr/bin/slirp4netns appartient à slirp4netns 1.1.12-1
version: |-
slirp4netns version 1.1.12
commit: 7a104a101aa3278a2152351a082a6df71f57c9a3
libslirp: 4.6.1
SLIRP_CONFIG_VERSION_MAX: 3
libseccomp: 2.5.2
swapFree: 17179865088
swapTotal: 17179865088
uptime: 6h 47m 57.51s (Approximately 0.25 days)
plugins:
log:
- k8s-file
- none
- journald
network:
- bridge
- macvlan
volume:
- local
registries:
docker.io:
Blocked: false
Insecure: false
Location: docker.io
MirrorByDigestOnly: false
Mirrors: null
Prefix: docker.io
search:
- docker.io
store:
configFile: /etc/containers/storage.conf
containerStore:
number: 1
paused: 0
running: 0
stopped: 1
graphDriverName: overlay
graphOptions:
overlay.mountopt: nodev
graphRoot: /var/lib/containers/storage
graphStatus:
Backing Filesystem: btrfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "true"
imageStore:
number: 11
runRoot: /run/containers/storage
volumePath: /var/lib/containers/storage/volumes
version:
APIVersion: 3.4.0
Built: 1633083258
BuiltTime: Fri Oct 1 12:14:18 2021
GitCommit: 6e8de00bb224f9931d7402648f0177e7357ed079
GoVersion: go1.17.1
OsArch: linux/amd64
Version: 3.4.0
Package info:
$ pacman -Qs podman
local/podman 3.4.0-1
Tool and library for running OCI-based containers in pods
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
I checked the guide.
It's the latest version that Manjaro OS offers.