Expected behavior
Docker should be able to start container images.
Actual behavior
Docker fails to start any container image with the same message error.
Steps to reproduce the behavior
Install docker on Fedora 34 (kernel version 5.12.15-300.fc34.x86_64) and try running (for example) the hello-world image.
The output you obtain is the following:
docker: Error response from daemon: OCI runtime create failed: 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: cannot fetch program from id: get program by id: permission denied: unknown.
ERRO[0000] error waiting for container: context canceled
It must be noted that adding the kernel parameter solves the issue on my machine, but, from my understanding, it shouldn't be necessary in the first place:
systemd.unified_cgroup_hierarchy=0
Output of docker version:
Client: Docker Engine - Community
Version: 20.10.7
API version: 1.41
Go version: go1.13.15
Git commit: f0df350
Built: Wed Jun 2 11:57:20 2021
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.7
API version: 1.41 (minimum version 1.12)
Go version: go1.13.15
Git commit: b0f5bc3
Built: Wed Jun 2 11:55:04 2021
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.8
GitCommit: 7eba5930496d9bbe375fdf71603e610ad737d2b2
runc:
Version: 1.0.0
GitCommit: v1.0.0-0-g84113ee
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Output of docker info:
Client:
Context: default
Debug Mode: false
Plugins:
app: Docker App (Docker Inc., v0.9.1-beta3)
buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
scan: Docker Scan (Docker Inc., v0.8.0)
Server:
Containers: 3
Running: 0
Paused: 0
Stopped: 3
Images: 10
Server Version: 20.10.7
Storage Driver: btrfs
Build Version: Btrfs v5.12.1
Library Version: 102
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 7eba5930496d9bbe375fdf71603e610ad737d2b2
runc version: v1.0.0-0-g84113ee
init version: de40ad0
Security Options:
seccomp
Profile: default
cgroupns
Kernel Version: 5.12.15-300.fc34.x86_64
Operating System: Fedora 34 (Workstation Edition)
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 31.01GiB
Name: deepthought
ID: W3QS:JLN5:OEFV:TZ6L:7223:XW53:JSUP:BKMY:DMXD:77D2:4TOU:ZT55
Docker Root Dir: /var/lib/docker
Debug Mode: false
Username: gabrieleara
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Additional environment details (AWS, VirtualBox, physical, etc.)
This is running on my physical machine, with the OS running on real hardware.
Expected behavior
Docker should be able to start container images.
Actual behavior
Docker fails to start any container image with the same message error.
Steps to reproduce the behavior
Install docker on Fedora 34 (kernel version
5.12.15-300.fc34.x86_64) and try running (for example) thehello-worldimage.The output you obtain is the following:
It must be noted that adding the kernel parameter solves the issue on my machine, but, from my understanding, it shouldn't be necessary in the first place:
Output of
docker version:Output of
docker info:Additional environment details (AWS, VirtualBox, physical, etc.)
This is running on my physical machine, with the OS running on real hardware.