podman: Rootless Containers: no such file or directory: OCI not found
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
-
Install RHEL 8.4
-
Install Podman
-
reboot
-
podman create docker.io/library/registry:2
-
podman start container_name Describe the results you received: Error: unable to start container “2820a02215ef24c41d2eee82167c1a911cbfd44e6b8d9649295dcdacf4639d0b”: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: open /sys/fs/cgroup/user.slice/user-1007.slice/user@1007.service/user.slice/libpod-2820a02215ef24c41d2eee82167c1a911cbfd44e6b8d9649295dcdacf4639d0b.scope/pids.max: no such file or directory: OCI runtime attempted to invoke a command that was not found
Describe the results you expected: Expected the system to start the container
Additional information you deem important (e.g. issue happens only occasionally): Allways - On around 4 identical machines
Output of podman version:
Version: 3.2.3
API Version: 3.2.3
Go Version: go1.15.7
Built: Tue Jul 27 07:29:39 2021
OS/Arch: linux/amd64
Output of podman info --debug:
host:
arch: amd64
buildahVersion: 1.21.3
cgroupControllers: []
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.0.29-1.module+el8.4.0+11822+6cc1e7d7.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.0.29, commit: ae467a0c8001179d4d0adf4ada381108a893d7ec'
cpus: 4
distribution:
distribution: '"rhel"'
version: "8.4"
eventLogger: file
hostname: svd-log-01
idMappings:
gidmap:
- container_id: 0
host_id: 1008
size: 1
- container_id: 1
host_id: 200000
size: 1001
- container_id: 1002
host_id: 558752
size: 65536
uidmap:
- container_id: 0
host_id: 1007
size: 1
- container_id: 1
host_id: 200000
size: 1001
- container_id: 1002
host_id: 558752
size: 65536
kernel: 4.18.0-305.12.1.el8_4.x86_64
linkmode: dynamic
memFree: 15014359040
memTotal: 16546336768
ociRuntime:
name: runc
package: runc-1.0.0-74.rc95.module+el8.4.0+11822+6cc1e7d7.x86_64
path: /usr/bin/runc
version: |-
runc version spec: 1.0.2-dev
go: go1.15.13
libseccomp: 2.5.1
os: linux
remoteSocket:
path: /run/user/1007/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_NET_RAW,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: true
seccompEnabled: true
seccompProfilePath: /usr/share/containers/seccomp.json
selinuxEnabled: true
serviceIsRemote: false
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.1.8-1.module+el8.4.0+11822+6cc1e7d7.x86_64
version: |-
slirp4netns version 1.1.8
commit: d361001f495417b880f20329121e3aa431a8f90f
libslirp: 4.3.1
SLIRP_CONFIG_VERSION_MAX: 3
libseccomp: 2.5.1
swapFree: 4294963200
swapTotal: 4294963200
uptime: 18m 2.15s
registries:
search:
- registry.access.redhat.com
- registry.redhat.io
- docker.io
store:
configFile: /home/container/.config/containers/storage.conf
containerStore:
number: 4
paused: 0
running: 0
stopped: 4
graphDriverName: overlay
graphOptions:
overlay.mount_program:
Executable: /usr/bin/fuse-overlayfs
Package: fuse-overlayfs-1.6-1.module+el8.4.0+11822+6cc1e7d7.x86_64
Version: |-
fusermount3 version: 3.2.1
fuse-overlayfs: version 1.6
FUSE library version 3.2.1
using FUSE kernel interface version 7.26
graphRoot: /home/container/.local/share/containers/storage
graphStatus:
Backing Filesystem: xfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "false"
imageStore:
number: 2
runRoot: /tmp/podman-run-1007/containers
volumePath: /home/container/.local/share/containers/storage/volumes
version:
APIVersion: 3.2.3
Built: 1627370979
BuiltTime: Tue Jul 27 07:29:39 2021
GitCommit: ""
GoVersion: go1.15.7
OsArch: linux/amd64
Version: 3.2.3
Package info (e.g. output of rpm -q podman or apt list podman):
podman-3.2.3-0.10.module+el8.4.0+11989+6676f7ad.x86_64
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.): Virtual machine, loginctl enable-linger for user enabled
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 18 (4 by maintainers)
i reloaded systemd deamon and it worked.
sudo systemctl daemon-reload
ah i missed reading https://github.com/containers/podman/issues/11197#issuecomment-896914876 , but indeed error message does not seems related at all 😕 . @Hyper200 is this resolved for you by making sure user sessions are up.
@mheon @giuseppe I am not sure but should we check at podman layer if there are no sessions available and end early with more intuitive error message ?
Hm. That’s actually a very strange error message for a missing systemd user session - I would have expected us to blow up trying to talk to the systemd dbus session in order to create a cgroup (which would also be a bad error message, but would provide a lot more breadcrumbs than this one).