Docker Community Forums

Share and learn in the Docker community.

Docker 1.4.0 daemon on Ubunto 14.04 does not start when installing with curl


(Kwolcott) #1

Hi;

Docker 1.4.0 daemon Ubunto 14.04 does not start by curl install method suggested by the docs.

Cannot seem to start the docker daemon manually either on Ubuntu

My Ubuntu 14.04 (server) is a VirtualBox guest on a Mac Book Pro running Yosemite.

Thanks,
Ken Wolcott


(Sven Dowideit) #2

what output do you get if you run sudo docker -D -d ?


(Kwolcott) #3

Hi Sven;

sudo docker -D -d
INFO[0000] +job serveapi(unix:///var/run/docker.sock)
INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
DEBU[0000] Registering GET, /version
DEBU[0000] Registering GET, /images/viz
DEBU[0000] Registering GET, /containers/ps
DEBU[0000] Registering GET, /containers/{name:.}/top
DEBU[0000] Registering GET, /info
DEBU[0000] Registering GET, /events
DEBU[0000] Registering GET, /images/json
DEBU[0000] Registering GET, /images/get
DEBU[0000] Registering GET, /images/{name:.
}/get
DEBU[0000] Registering GET, /images/{name:.}/history
DEBU[0000] Registering GET, /images/{name:.
}/json
DEBU[0000] Registering GET, /_ping
DEBU[0000] Registering GET, /containers/{name:.}/logs
DEBU[0000] Registering GET, /exec/{id:.
}/json
DEBU[0000] Registering GET, /containers/{name:.}/changes
DEBU[0000] Registering GET, /containers/json
DEBU[0000] Registering GET, /containers/{name:.
}/export
DEBU[0000] Registering GET, /containers/{name:.}/json
DEBU[0000] Registering GET, /containers/{name:.
}/attach/ws
DEBU[0000] Registering GET, /images/search
DEBU[0000] Registering POST, /auth
DEBU[0000] Registering POST, /exec/{name:.}/start
DEBU[0000] Registering POST, /exec/{name:.
}/resize
DEBU[0000] Registering POST, /containers/{name:.}/start
DEBU[0000] Registering POST, /images/create
DEBU[0000] Registering POST, /images/load
DEBU[0000] Registering POST, /images/{name:.
}/push
DEBU[0000] Registering POST, /containers/{name:.}/wait
DEBU[0000] Registering POST, /containers/{name:.
}/attach
DEBU[0000] Registering POST, /containers/{name:.}/copy
DEBU[0000] Registering POST, /containers/{name:.
}/exec
DEBU[0000] Registering POST, /build
DEBU[0000] Registering POST, /containers/{name:.}/unpause
DEBU[0000] Registering POST, /containers/{name:.
}/restart
DEBU[0000] Registering POST, /containers/{name:.}/kill
DEBU[0000] Registering POST, /containers/{name:.
}/pause
DEBU[0000] Registering POST, /containers/{name:.}/stop
DEBU[0000] Registering POST, /containers/{name:.
}/resize
DEBU[0000] Registering POST, /commit
DEBU[0000] Registering POST, /images/{name:.}/tag
DEBU[0000] Registering POST, /containers/create
DEBU[0000] Registering DELETE, /containers/{name:.
}
DEBU[0000] Registering DELETE, /images/{name:.*}
DEBU[0000] Registering OPTIONS,
DEBU[0000] docker group found. gid: 999
DEBU[0000] Generated prefix: docker-252:0-4066956
DEBU[0000] Checking for existence of the pool 'docker-252:0-4066956-pool’
DEBU[0000] Pool doesn’t exist. Creating it.
DEBU[0000] libdevmapper(3): ioctl/libdm-iface.c:1768 (-1) device-mapper: reload ioctl on docker-252:0-4066956-pool failed: Invalid argument
FATA[0000] Error running DeviceCreate (CreatePool) dm_task_run failed

Thanks,
Ken Wolcott


(Kwolcott) #4

Here are some docker-related events from dmesg:

dmesg | grep -i docker
[ 20.331703] init: docker main process (748) terminated with status 1
[ 20.331724] init: docker main process ended, respawning
[ 20.471258] init: docker main process (1131) terminated with status 1
[ 20.471279] init: docker main process ended, respawning
[ 20.608658] init: docker main process (1173) terminated with status 1
[ 20.608672] init: docker main process ended, respawning
[ 20.775119] init: docker main process (1217) terminated with status 1
[ 20.775131] init: docker main process ended, respawning
[ 20.901520] init: docker main process (1261) terminated with status 1
[ 20.901555] init: docker main process ended, respawning
[ 21.025988] init: docker main process (1303) terminated with status 1
[ 21.026008] init: docker main process ended, respawning
[ 21.148376] init: docker main process (1345) terminated with status 1
[ 21.148398] init: docker main process ended, respawning
[ 21.289679] init: docker main process (1389) terminated with status 1
[ 21.289697] init: docker main process ended, respawning
[ 21.410473] init: docker main process (1445) terminated with status 1
[ 21.410499] init: docker main process ended, respawning
[ 21.540392] init: docker main process (1487) terminated with status 1
[ 21.540405] init: docker main process ended, respawning
[ 21.685201] init: docker main process (1529) terminated with status 1
[ 21.685241] init: docker respawning too fast, stopped


(Sven Dowideit) #5

mm, ok, I’m going to suspect that your devicemapper package is out of date, but

can you post the output from docker -D info and docker version

are you able to do an apt-get upgrade?


(Thomas) #6

My x64 vserver running Debian Wheezy has the same problem (dm_task_run failed). The docs tell me to install a backported kernel 3.14, but the backport now is at kernel 3.16, and my fully updated Wheezy already runs 3.14. The installation shell script runs apt-get install -y -q linux-image-extra-3.14.17, but this package isn’t available anymore. I also tried updating the kernel to 3.16, but the shell script still attempts to install the package for kernel 3.14. My desktop machine runs Ubuntu 14.04 (kernel 3.13), but I won’t try to install docker here, since I need this machine to get things done :wink:


(Sven Dowideit) #7

I wonder

the https://get.docker.com script actually tries to install kern_extras="linux-image-extra-$(uname -r)"

so I’ll have to ask - are you sure you rebooted after you upgraded your kernel packages?


(Thomas) #8

Sven, yes, I did reboot (but I can see why you’re asking :wink: ). However, your hint was really good! Obviously, something went really wrong with upgrading my XEN vserver instance from Debian 6 to Debian 7.5. After the backport kernel installation ‘uname -r’ still prints 3.14.17, while ‘ls /lib/modules’ shows me ´2.6.32-5-xen-amd64’, and ‘3.16.0-0.bpo.4-amd64’. I guess I’d better clean this up, and then give ‘get.docker.com’ one more try.
Thanks for your help & Happy New Year!


(Kwolcott) #9

Hi Sven;

Is there an update for this docker daemon refusing to start issue?

Thanks,
Ken


(Sven Dowideit) #10

Heya Ken

did you update your kernel and devicemapper packages?

Sven


(Kwolcott) #11

Hi Sven;

As a result of this and several other issues (not related to Docker), I
completely removed the vm in question and I have not seen the problem
re-appear in any subsequent vm.

Thanks for following up.

Ken Wolcott