On 3/3/20 12:13 PM, Adrian Reber wrote: > On Tue, Mar 03, 2020 at 12:06:11PM -0500, Steve Dickson wrote: >> I'm trying to start the docker service on F31 (5.5.7-200.fc31.x86_64) >> and I'm getting the following error >> >> ? docker.service - Docker Application Container Engine >> Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled) >> Active: failed (Result: exit-code) since Tue 2020-03-03 11:36:19 EST; 1min 37s ago >> Docs: http://docs.docker.com >> Process: 6855 ExecStart=/usr/bin/dockerd-current --add-runtime oci=/usr/libexec/docker/docker-runc-current --default-runtime=oci --authorization-plugin=rhel-push-plugin --containerd /run/containerd.sock --exec-opt native.cgroupdriver=systemd --userland-proxy-path=/usr/libexec/docker/docker-proxy-current --init-path=/usr/libexec/docker/docker-init-current --seccomp-profile=/etc/docker/seccomp.json $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY $REGISTRIES (code=exited, status=1/FAILURE) >> Main PID: 6855 (code=exited, status=1/FAILURE) >> CPU: 124ms >> >> time="2020-03-03T11:36:19.140274478-05:00" level=info msg="Graph migration to content-addressability took 0.00 seconds" >> time="2020-03-03T11:36:19.141106888-05:00" level=warning msg="Your kernel does not support cgroup memory limit" >> time="2020-03-03T11:36:19.141141530-05:00" level=warning msg="Unable to find cpu cgroup in mounts" >> time="2020-03-03T11:36:19.141158734-05:00" level=warning msg="Unable to find blkio cgroup in mounts" >> time="2020-03-03T11:36:19.141175193-05:00" level=warning msg="Unable to find cpuset cgroup in mounts" >> time="2020-03-03T11:36:19.141249230-05:00" level=warning msg="mountpoint for pids not found" >> Error starting daemon: Devices cgroup isn't mounted >> docker.service: Main process exited, code=exited, status=1/FAILURE >> docker.service: Failed with result 'exit-code'. >> Failed to start Docker Application Container Engine. >> >> Is there no cgroup support in the current f31 kernel? > > Fedora 31 defaults to cgroup2 and you can either use Podman with cgroup2 > support or reboot with cgroup1 support using the kernel command-line: > > systemd.unified_cgroup_hierarchy=0 Interesting.... Thanks for the info! steved. > > Adrian > _______________________________________________ > kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx
