docker not installing about docker HOT 9 CLOSED

I'm hitting this issue as well. The cookbook works when deployed to any server that is running a 3.8 kernel. I'm testing on Rackspace, and I hit this issue:

root@bacongobbler:~# docker -d
2014/03/05 20:00:51 WARNING: You are running linux kernel version 3.2.0-59-virtual, which might be unstable running docker. Please upgrade your kernel to 3.8.0.
[/var/lib/docker|4dd4db35] +job initserver()
[/var/lib/docker|4dd4db35.initserver()] Creating server
[/var/lib/docker|4dd4db35] +job init_networkdriver()
[/var/lib/docker|4dd4db35] -job init_networkdriver() = OK (0)
Loading containers: : done.
[/var/lib/docker|4dd4db35.initserver()] Creating pidfile
[/var/lib/docker|4dd4db35.initserver()] Setting up signal traps
[/var/lib/docker|4dd4db35] -job initserver() = OK (0)
[/var/lib/docker|4dd4db35] +job serveapi(unix:///var/run/docker.sock)
2014/03/05 20:00:52 Listening for HTTP on unix (/var/run/docker.sock)

However, when I run start docker:

root@bacongobbler:~# start docker
docker start/running, process 3831
root@bacongobbler:~# tail /var/log/syslog
Mar  5 20:04:26 bacongobbler-image kernel: [  985.199641] init: docker main process (3875) terminated with status 1
Mar  5 20:04:26 bacongobbler-image kernel: [  985.199683] init: docker main process ended, respawning
Mar  5 20:04:26 bacongobbler-image kernel: [  985.219504] init: docker main process (3882) terminated with status 1
Mar  5 20:04:26 bacongobbler-image kernel: [  985.219544] init: docker main process ended, respawning
Mar  5 20:04:26 bacongobbler-image kernel: [  985.239113] init: docker main process (3890) terminated with status 1
Mar  5 20:04:26 bacongobbler-image kernel: [  985.239153] init: docker main process ended, respawning
Mar  5 20:04:26 bacongobbler-image kernel: [  985.258796] init: docker main process (3898) terminated with status 1
Mar  5 20:04:26 bacongobbler-image kernel: [  985.258836] init: docker main process ended, respawning
Mar  5 20:04:26 bacongobbler-image kernel: [  985.278643] init: docker main process (3905) terminated with status 1
Mar  5 20:04:26 bacongobbler-image kernel: [  985.278683] init: docker respawning too fast, stopped

And my kernel version:

root@bacongobbler:~# uname -a
Linux bacongobbler 3.2.0-59-virtual #90-Ubuntu SMP Tue Jan 7 23:02:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

from docker.

Yeah fix to this is to upgrade the kernel to 3.8 and then run the cookbook. That ended up being what I did to get it working.

from docker.

Good to close?

from docker.

Unfortunately I don't think this cookbook should handle kernel upgrades;
seems like yak shaving and risky. Would it make sense if this cookbook
threw a WARN with a helpful message on non-RHEL platforms below kernel 3.8?

On Wed, Mar 5, 2014 at 3:10 PM, James Wickett [email protected]:

Yeah fix to this is to upgrade the kernel to 3.8 and then run the
cookbook. That ended up being what I did to get it working.

Reply to this email directly or view it on GitHubhttps://github.com//issues/75#issuecomment-36787538
.

Brian Flad
http://about.me/bflad

from docker.

I don't think so either. I was just posting my log output to confirm that this was what happened. I
stumbled upon this by accident; I thought my kernel was already above 3.8!

Would it make sense if this cookbook
threw a WARN with a helpful message on non-RHEL platforms below kernel 3.8?

I think some documentation that this cookbook requires a 3.8+ kernel on the host would be more than
acceptable.

On 2014-03-05, 1:03 PM, Brian Flad wrote:

Unfortunately I don't think this cookbook should handle kernel upgrades;
seems like yak shaving and risky. Would it make sense if this cookbook
threw a WARN with a helpful message on non-RHEL platforms below kernel 3.8?

On Wed, Mar 5, 2014 at 3:10 PM, James Wickett [email protected]:

Yeah fix to this is to upgrade the kernel to 3.8 and then run the
cookbook. That ended up being what I did to get it working.

Reply to this email directly or view it on
GitHubhttps://github.com//issues/75#issuecomment-36787538
.

Brian Flad
http://about.me/bflad

—
Reply to this email directly or view it on GitHub
#75 (comment).

from docker.

+1

I think some documentation that this cookbook requires a 3.8+ kernel on the host would be more than acceptable.

from docker.

I have the same problem, on ubuntu 13.10.

Running docker from the command-line works fine, but, the upstart service is broken.

Same dmesg errors reported above:

[  162.585545] init: docker main process (4725) terminated with status 1
[  162.585567] init: docker respawning too fast, stopped

Checking the upstart log I got a hint as to root cause:

$ sudo tail -n1 /var/log/upstart/docker.log
2014/03/06 20:19:37 initserver: AUFS was not found in /proc/filesystems

The docker documentation states how to install the optional AUFS file support so the following work-around solved my issue:

include_recipe "docker"

package "linux-image-extra-#{node[:kernel][:release]}" do
  notifies :restart, 'service[docker]', :immediately
end

Docker has a well documented installation approach for each Ubuntu version. What is wrong with applying these from this cookbook? This behaviour could be made optional. At the very least some run-time warnings would assist newcomers.

from docker.

When Ubuntu 13.10 was added, I believe it was submitted excluding the AUFS package install for whatever reason. Since we've added the ability to disable messing with storage driver support, I'm thinking that we can remove that exclusion and let the aufs recipe do its thing (if its called). I can fix this tonight.

from docker.

I missed the significance of the "storage_type" attribute.

Yes, installing the missing package as the default "aufs" behaviour would certainly help. Thank you.

from docker.