Docker Install: Error running DeviceCreate (createPool) dm_task_run failed #6325
Comments
|
ping @alexlarsson |
|
I was having the same problem and fixed it adding CONFIG_DM_THIN_PROVISIONING option on the kernel. |
|
I changed It went a bit ahead now, but failed with unknown reason: @m0ikz Thanks for your help. Any idea if you stuck further after that. |
|
I wonder why it didn't auto-load the dm_thin_pool module. Can you try running |
|
I think even |
|
Yeah, that doesn't really give a lot more info. Can you try running docker under strace: |
|
We bumped into just the same situation as you did. We did the following and the issue seemed to be solved:
|
|
I ran into this when changing my kernel as well. Went from 3.13 on 14.04 to 3.2 trying to enable swap limit support (digital ocean is lagging behind on this). It was fixed by going back to the old kernel however. |
|
Hitting this now on master (aec8d90) and 3.14.9-200.fc20.x86_64 |
|
ah, need to include |
|
hello, guys. ~ # uname -a ~ # docker -v ~ # docker -D -d |
|
For those who are running into this problem, could you try running this [1] script and comment if you're seeing anything missing in the devicemapper section, please? [1] https://raw.githubusercontent.com/dotcloud/docker/master/contrib/check-config.sh |
|
I broke a server after trying to install Shipyard... How bad is this? My kernel's version is way older!!! Is there any other workaround to other than reinstall the host with the latest REHL7? @unclejack, what do you think? [root@pppdc9prd4c4 ~]# . check-config.sh Generally Necessary:
Optional Features:
|
|
@marcellodesales did you add |
|
@vbatts, I tried different options here and I couldn't get it running :( Could you share an example of how the file looks like with that... The following are my attempts to get it working... I tried to execute it directly in the command-line as well... Then, I tried with the contents updated... With those attempts, the daemon does not start, even though it is reported to be running... I tried other formats :S, removing the quotes, etc... And defining it in a new line, but docker complained about the "format and command"... Failed with command not found... |
|
Also, after the attempts to run this, I can't start docker on my machine anymore :( I reverted the config and tried executing it again and Docker can't start... Trying to use docker -d |
|
I received this error when docker used up all it's disk space. I went and removed a bunch of images to free some space up, but any time I tried to start a container, it threw the Going to have to wipe the docker partition and start over. |
|
#4202 has backend-specific operations, including pool resizing. That would partly help the disk space issue (by allowing you to avoid it ahead of time). I think what is happening here is that the pool gets into some kind of error state that we have to handle, maybe with some kind of pool-fsck command. |
|
@phemmer, I can confirm the error is related to the partition being out of space! |
|
I have the same problem. Error running DeviceCreate (createPool) dm_task_run failed How do I recover Docker containers and images from the disk? |
|
@fosstamil Did you check if you have enough space in the partition where you images are created? The images are stored under /var/lib/docker ? (or any other dir you configured the libs to be?) |
|
i broke a server (digital-ocean), moving it to another data-center. @unclejack output from check-config: Tried all the things above
$ docker -d -D |
|
@fracklen Please upgrade your kernel to something supported. The LTS trusty kernel image is also available for 12.04. 3.8 is no longer supported by anyone, including Canonical. |
|
@unclejack upgraded to 3.13 - no luck - what's next? |
|
Are you using digital ocean? I was once suffering from the same problem until I run locate ".config" and then switched my kernel to one shown at the last command.
This worked for me, please try if this works for you as well. |
|
@xiaokangwang yep. It appears to be a problem with DigitalOcean. Somehow there was an inconsistency between the actual kernel and the one Ubuntu had installed / used by grub. We switched the kernel in their interface and the problem persisted. Only when we moved the image to another vps and in the process updated the kernel - both grub and DO-interface, the problem went away. |
|
I had the same "mixed up kernels" issue on DigitalOcean after migrating an I fixed it by installing the kernel specified by
|
|
@liquid |
|
@marvell I've changed back to the original kernel and I've still got no luck :( |
|
@liquid Try reinstall docker: |
|
this helped for me: sudo apt-get install linux-image-extra-`uname -r` |
|
@vbatts Can you please tell me a way to resolve this and to start my container? docker info |
|
@sahus5 is your root file system on lvm? If so, it would be best to make an actual volume block device that is a thin pool to start docker with. |
|
I ran into this error, and the problem was that my root fs had run out of space |
|
One of the application was writing logs to rootfs and it ran out of space. |
|
Can also confirm that like @francisdb with the latest kernel the fix was: |
|
Hi, How did you guys fix it. 2015/07/10 14:06:48 docker daemon: 1.3.3 17fec36-dirty; execdriver: native; graphdriver: [Switch_1_RP_0:/usr/bin]$ uname -a [Switch_1_RP_0:/usr/bin]$ docker --version [Switch_1_RP_0:/usr/bin]$ docker info Please Help, Stuck here from long Nasrulla |
|
I am having this issue on CentOS-7 - can anyone help? uname -a: Linux localhost.localdomain 3.10.0-229.7.2.el7.x86_64 #1 SMP Tue Jun 23 22:06:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux docker version:Client version: 1.6.2 docker info:Containers: 0 Steps to reproduce: docker -d -D2.) run "docker pull hello-world" in another terminal window These steps were all run as root and root is a member of the "docker" group. Is there any hope of running docker on CentOS-7? |
@francisdb thank you! :) |
|
Also having the issue on CentOS 7. Daemon start: Error generated by: Output inside daemon: Docker info: Kernel: OS: Running on physical machine (localhost @ my room) with no virtualization. Any help would be greatly appreciated! EDIT: EDIT2: The error seems pretty serious as it crashes the daemon with a EDIT3: EDIT4: /b3 |
|
Seriously? A reproduceable Panic in the docker daemon and no reaction from the devs after 10 days? Have they taken the money and left? |
|
I had the same problem and was not able to fix it because I did'nt want to go for the full nuke: /var/lib/docker/ solution. |
|
Had the same issue following the tutorial @ http://docs.docker.com/engine/installation/ubuntulinux/ on ubuntu trusty. But "sudo apt-get install linux-image-extra-uname -r" did the trick, thanks @francisdb ! |
|
uname -a docker version docker info |
|
version is : what's wrong with "Cannot connect to the Docker daemon. Is the docker daemon running on this host?" ? ubuntu kernel version is : |
|
---ok , I konw it is that my kernel is too lower,--- |
TL;DRI'm constantly corrupting my /var/lib/docker directory by running docker in loopback mode when I MEAN to run in devicemapper mode. To fix without rebooting/deleting the ENTIRE /var/lib/docker dir (as root)
ExplanationI'm not sure if this is of any help, but I am CONTINUOUSLY having this problem too! Now the reason I get this is VERY reproducible and fixable. (NO, NOT BY DELETING /var/lib/docker!!!) In my case, I run docker via Which I add to Edit: However I have discovered that it is important to clean up the loop back devices properly BEFORE deleting /var/lib/docker/devicemapper/devicemapper/, or else you have stray loopbacks that need to be cleaned up (via rebooting?) Recap
Running CentOS 7.2.1511
As a side note, the third time I tried this, I had to delete |
|
Any guidelines on figuring this out?? |
Works for me. |
|
Hi, installed docker on my wheezy and have the same problem, the service does not start Linux s17367650 3.10.32-20140228a #1 SMP Fri Feb 28 08:17:48 UTC 2014 x86_64 GNU/Linux Client: And this is what the logfile says: time="2016-09-13T04:13:13.479620266+02:00" level=info msg="libcontainerd: new containerd process, pid: 12201" I followed this installation guide: https://docs.docker.com/engine/installation/linux/debian/ |
|
Hey, I am hitting this now. These are the results of check-config.sh: Any idea what's causing these corruptions? We are hitting this quite a lot. |
and others
I followed all steps given in the installation guide for 12.04
But, it fails when starting the docker daemon:
Ubuntu version:
Linux Header version:
Could not find this error anywhere online. Any cues appreciated.
The text was updated successfully, but these errors were encountered: