[Bug 1217613] New: Cannot start container [8] System error: mountpoint for cpuset not found
https://bugzilla.redhat.com/show_bug.cgi?id=1217613
Bug ID: 1217613 Summary: Cannot start container [8] System error: mountpoint for cpuset not found Product: Fedora Version: 21 Component: docker-io Assignee: ichavero@redhat.com Reporter: jiri.folta@centrum.cz QA Contact: extras-qa@fedoraproject.org CC: adimania@gmail.com, admiller@redhat.com, golang@lists.fedoraproject.org, hushan.jia@gmail.com, ichavero@redhat.com, jchaloup@redhat.com, jperrin@centos.org, lsm5@redhat.com, mattdm@redhat.com, mgoldman@redhat.com, miminar@redhat.com, s@shk.io, thrcka@redhat.com, vbatts@redhat.com
Created attachment 1020711 --> https://bugzilla.redhat.com/attachment.cgi?id=1020711&action=edit screenshot of the error
Description of problem: when trying to run a container using Cockpit I get "System error: mountpoint for cpuset not found" error
Version-Release number of selected component (if applicable): cockpit: Version 0.27. Built on Wed Mar 25 12:53:20 UTC 2015.
How reproducible: allways
Steps to Reproduce: 1.Install minimal Fedora 21 for arm platform from http://www.digitaldreamtime.co.uk/images/Fidora/21/ 2.update the system 3.install cockpit and docker 4.login to the server using web interface https://ip:9090 5.download Image: docker.io/wordpress:latest 6. try running the image
Actual results: you get an error message(attached)
Expected results: actually running the image
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1217613
--- Comment #1 from Jirka Folta jiri.folta@centrum.cz --- [root@fidora-minimal-remix ~]# docker info Containers: 1 Images: 33 Storage Driver: devicemapper Pool Name: docker-179:3-127068-pool Pool Blocksize: 65.54 kB Backing Filesystem: extfs Data file: /dev/loop0 Metadata file: /dev/loop1 Data Space Used: 934.5 MB Data Space Total: 107.4 GB Data Space Available: 28.01 GB Metadata Space Used: 2.003 MB Metadata Space Total: 2.147 GB Metadata Space Available: 2.145 GB Udev Sync Supported: true Data loop file: /var/lib/docker/devicemapper/devicemapper/data Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata Library Version: 1.02.93 (2015-01-30) Execution Driver: native-0.2 Kernel Version: 3.18.12-501.20150429git2747cc0.sc20.armv7hl.bcm2709 Operating System: Fedora 21 (Twenty One) CPUs: 4 Total Memory: 974.7 MiB Name: fidora-minimal-remix ID: 5UQ7:IPRF:NNL4:QMQQ:IVQU:QEPE:HHYH:WA75:LURE:4US5:LA6J:IULE WARNING: No memory limit support WARNING: No swap limit support [root@fidora-minimal-remix ~]# sudo docker version Client version: 1.6.0 Client API version: 1.18 Go version (client): go1.4.2 Git commit (client): 3eac457/1.6.0 OS/Arch (client): linux/arm Server version: 1.6.0 Server API version: 1.18 Go version (server): go1.4.2 Git commit (server): 3eac457/1.6.0 OS/Arch (server): linux/arm
[root@fidora-minimal-remix ~]# cat /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpu 2 51 1 cpuacct 2 51 1 memory 0 1 0 devices 3 51 1 freezer 4 5 1 net_cls 5 1 1 blkio 6 51 1
[root@fidora-minimal-remix ~]# cat /etc/redhat-release Fedora release 21 (Twenty One)
https://bugzilla.redhat.com/show_bug.cgi?id=1217613
Jan Chaloupka jchaloup@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jiri.folta@centrum.cz Flags| |needinfo?(jiri.folta@centru | |m.cz)
--- Comment #2 from Jan Chaloupka jchaloup@redhat.com --- Hi Jirka,
it looks like cgroups are not mounted for docker. This is more like cockpit issue.
Can you run ls /sys/fs/cgroup/ on the f21 machine and inside docker?
Jan
https://bugzilla.redhat.com/show_bug.cgi?id=1217613
Jirka Folta jiri.folta@centrum.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jiri.folta@centru | |m.cz) |
--- Comment #3 from Jirka Folta jiri.folta@centrum.cz --- Hey, Jan here you go:
[root@fidora-minimal-remix ~]# ls /sys/fs/cgroup/ blkio cpu cpuacct cpu,cpuacct devices freezer net_cls systemd
https://bugzilla.redhat.com/show_bug.cgi?id=1217613
Jan Chaloupka jchaloup@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |puiterwijk@redhat.com, | |stefw@redhat.com Component|docker-io |cockpit Assignee|ichavero@redhat.com |stefw@redhat.com
--- Comment #4 from Jan Chaloupka jchaloup@redhat.com --- Thanks Jirka.
This looks like cockpit is running docker without mounted cgroups.
https://bugzilla.redhat.com/show_bug.cgi?id=1217613
Stef Walter stefw@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|stefw@redhat.com |dperpeet@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1217613
Dominik Perpeet dperpeet@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jiri.folta@centru | |m.cz)
--- Comment #5 from Dominik Perpeet dperpeet@redhat.com --- Hi Jirka,
have you tried running the docker command manually in the shell for comparison (not in cockpit)? e.g. "docker run docker.io/wordpress:latest"
As far as I know we don't access cpuset from inside cockpit and we only interface with a running docker instance. If docker isn't running we offer to start it for the user, which is internally done via "systemctl start docker".
If it works in the console and not in cockpit, could you also please test running a simple container like busybox via cockpit?
Dominik
https://bugzilla.redhat.com/show_bug.cgi?id=1217613
--- Comment #6 from Fedora End Of Life endoflife@fedoraproject.org --- This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
https://bugzilla.redhat.com/show_bug.cgi?id=1217613
Jan Kurik jkurik@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |EOL Last Closed| |2015-12-02 14:48:19
https://bugzilla.redhat.com/show_bug.cgi?id=1217613
--- Comment #7 from Jan Kurik jkurik@redhat.com --- Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
golang@lists.fedoraproject.org
-
Red Hat Bugzilla