moby: Docker in Docker - failed to find the cgroup root
Hi all,
I am running 1.3 on RHEL7 with a priv container running ubuntu 14:04 and 1.3 under it. Everything is running, however, in jenkins (the container running docker within), I am getting the following:
Sending build context to Docker daemon
Step 0 : FROM ubuntu:latest
---> 5506de2b643b
Step 1 : MAINTAINER Aaron Nicoli <aaronnicoli@gmail.com>
---> Running in 88aa05a47854
---> 23620994a830
Removing intermediate container 88aa05a47854
Step 2 : ENV DEBIAN_FRONTEND noninteractive
---> Running in 8462b83bec13
---> 6aa5870a3b2d
Removing intermediate container 8462b83bec13
Step 3 : RUN rm -f /etc/localtime
---> Running in 0f2bcc9197b8
Removing intermediate container 0f2bcc9197b8
2014/10/27 14:12:23 failed to find the cgroup root
Build step 'Execute shell' marked build as failure
Finished: FAILURE
Any thoughts? I can’t see any issues, but, then again… I am no expert.
root@02eff186c45b:/# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/docker-8:49-1310721-02eff186c45bd6dd568a909b7fb7e86cd92a8599b2921c6e558ad21627a705cf 9.8G 735M 8.5G 8% /
tmpfs 3.9G 0 3.9G 0% /dev
shm 64M 0 64M 0% /dev/shm
/dev/sdd1 40G 3.6G 34G 10% /etc/hosts
/dev/sdc1 16G 491M 15G 4% /var/jenkins_home
cgroup 3.9G 0 3.9G 0% /sys/fs/cgroup
I have /var/lib/docker listed as a volume in the Dockerfile (that the jenk container was built from).
Aaron.
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Comments: 22 (5 by maintainers)
Commits related to this issue
- Update libcontainer to 185328a42654f6dc9a41814e578 Mac address support to the netlink pkg. Cgroup performance and memory issues. Netlink refactoring. Signed-off-by: Michael Crosby <crosbymichael@gma... — committed to moby/moby by crosbymichael 10 years ago
- Cache cgroup root mount location. We calculate this on every cgroup call. It comprised of 30%+ of the CPU usage in cAdvisor. Docker-DCO-1.1-Signed-off-by: Victor Marmol <vmarmol@google.com> (github:... — committed to docker-archive/libcontainer by vmarmol 10 years ago
- Retry getting the cgroup root at apply time. This will allow late-binding of the cgroup hierarchy. Signed-off-by: Victor Marmol <vmarmol@google.com> — committed to vmarmol/libcontainer by vmarmol 9 years ago
- Retry getting the cgroup root at apply time. This will allow late-binding of the cgroup hierarchy. Fixes docker/docker#8791 Signed-off-by: Victor Marmol <vmarmol@google.com> — committed to vmarmol/libcontainer by vmarmol 9 years ago
- Retry getting the cgroup root at apply time. This will allow late-binding of the cgroup hierarchy. Fixes docker/docker#8791 Signed-off-by: Victor Marmol <vmarmol@google.com> — committed to vmarmol/libcontainer by vmarmol 9 years ago
- Retry getting the cgroup root at apply time. This will allow late-binding of the cgroup hierarchy. Fixes docker/docker#8791 Signed-off-by: Victor Marmol <vmarmol@google.com> — committed to mahak/libcontainer by vmarmol 9 years ago
This may help in debugging. Host docker is CoreOS 472 and guest docker is
dockerhub:flitter/builder:master
For anyone who may be having or is still having this issue on a RHEL server, would you be able to verify if the
libcgroup
package is installed usingsudo yum list installed libcgroup
? If it isn’t try installing it (sudo yum install libcgroup
).Assuming it is installed already, first of all, check the status:
If it is stopped, start it:
If it is already running, restart it:
The docker init script
/etc/init.d/docker
requires that thecgconfig
service be started but it sounds like one (or more) of the cgroup filesystems becomes unconfigured for whatever reason after the service is started so restarting it ought to resolve the issues.If it doesn’t, could someone post their
/etc/cgconfig.conf
and check to see if there are any files in/etc/cgconfig.d
?Thanks for this - this made docker-in-docker work for me:
https://github.com/ianmiell/shutit/commit/3d7238f02c23c40a34c5000c4e88f64565c3685c#diff-469a2a5ebd309b7bea7966e84b092112
Sending you a virtual beer/coffee/the purest water.