Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Machine stuck running DinD on CentOS 6.5 #11072

Closed
kashyap-parikh opened this issue Feb 28, 2015 · 7 comments
Closed

Machine stuck running DinD on CentOS 6.5 #11072

kashyap-parikh opened this issue Feb 28, 2015 · 7 comments

Comments

@kashyap-parikh
Copy link

I am trying to run DinD on CentOS 6.5 VM + Docker Version 1.3.2 running in virtualbox on a mac.
Using /fedora example I was able to build dind image. The only change I had to make was replacing CGROUP=/sys/fs/cgroup with CGROUP=/cgroup in wrapdocker.

When I try to start dind it freezes the host VM. Just before the freeze I see that mkfs.ext4 is using 100% cpu.

To reproduce:

vagrant box centos65 https://github.com/2creatives/vagrant-centos/releases/download/v6.5.3/centos65-x86_64-20140116.box
vagrant box init centos65
vagrant up
vagrant ssh
$ git clone git@github.com:jpetazzo/dind.git
$ cd dind/fedora
Change Dockerfile "FROM centos:6"
Change wrapdocker "CGROUP=/cgroup"
$ sudo ./build.sh
$ docker run --privileged -t -i -e DOCKER_DAEMON_ARGS="-D" dind

Here's the console log with last few lines before VM freezes. The only way to recover is shutdown and start.

@jessfraz
Copy link
Contributor

I think you forgot the link :/

@jessfraz
Copy link
Contributor

can you try with the latest version of docker also we need the output of docker version, docker info, uname -a

@kashyap-parikh
Copy link
Author

Below is uname and screenshot. Latest docker version for CentOS 6.5 is 1.4.1 and it has another issue #9856 that forced me to revert to 1.3.2.

[vagrant@vagrant-centos65 ~]$ uname -a
Linux vagrant-centos65.vagrantup.com 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

screen shot 2015-02-25 at 2 32 39 pm

@kashyap-parikh
Copy link
Author

docker info

[vagrant@vagrant-centos65 ~]$ sudo docker info
Containers: 1
Images: 30
Storage Driver: devicemapper
 Pool Name: docker-8:17-666002-pool
 Pool Blocksize: 65.54 kB
 Data file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
 Data Space Used: 7.581 GB
 Data Space Total: 107.4 GB
 Metadata Space Used: 5.005 MB
 Metadata Space Total: 2.147 GB
 Library Version: 1.02.89-RHEL6 (2014-09-01)
Execution Driver: native-0.2
Kernel Version: 2.6.32-431.3.1.el6.x86_64
Operating System: <unknown>

docker version

[vagrant@vagrant-centos65 ~]$ sudo docker version
Client version: 1.3.2
Client API version: 1.15
Go version (client): go1.3.3
Git commit (client): 39fa2fa/1.3.2
OS/Arch (client): linux/amd64
Server version: 1.3.2
Server API version: 1.15
Go version (server): go1.3.3
Git commit (server): 39fa2fa/1.3.2
[vagrant@vagrant-centos65 ~]$ 

@jessfraz
Copy link
Contributor

jessfraz commented Mar 2, 2015

ping @vbatts

thanks for the info @kashyap-parikh

@unclejack
Copy link
Contributor

@kashyap-parikh Please run yum update to update your CentOS system and reboot it afterwards.

@unclejack
Copy link
Contributor

I'm going to close this issue now because it's been reported against Docker 1.3.2 and kernel 2.6.32-431. There are newer kernels available for CentOS 6.x and they can be easily installed via yum update and they can be used by running reboot to start using them.

If you can reproduce this with a fully updated system, please comment on this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants