Docker-gitlab: docker respawning too fast, stopped

[infinitydeveloper]

==> /var/log/syslog <==
May 12 22:24:25 srv7 kernel: [ 1277.648130] init: docker main process (28969) terminated with status 1
May 12 22:24:25 srv7 kernel: [ 1277.648147] init: docker main process ended, respawning
May 12 22:24:25 srv7 kernel: [ 1278.000126] init: docker main process (29028) terminated with status 1
May 12 22:24:25 srv7 kernel: [ 1278.000144] init: docker respawning too fast, stopped

[infinitydeveloper]

ever when i try to service docker start, it doesn't start... instead it respawns too fast and then stops.

[sameersbn]

This looks like an issue with docker. You either need to report it on the docker projects issue page or at least provide some more information/context for me to give you some advise.

[thomasleveil]

take a look at your upstart log files. See http://www.tekhead.org/blog/2014/09/installing-docker-on-ubuntu-quick-fix/

[gyulaweber]

I had the same issue, (ubuntu trusty, 3.19.0-33), the /var/log/upstart/docker.log said that the graph driver in not supported.

I've installed the linux-image-extra-3.19.0-33-generic package (additional drivers), and it fixed the issue without reboot.

[sameersbn]

were you able to resolve this issue? can we close it?

[gyulaweber]

@infinitydeveloper - do you have any log files to see what's happening behind the scenes? (or it's already resolved?).

[thoriumbr]

On my Mint 17.3, I had the same problem. I solved it installing app-armor.

On this site (http://www.tekhead.org/blog/2014/09/installing-docker-on-ubuntu-quick-fix/) I saw the problem and the solution. Docker tries to load app-armor profile, fails and dies:

Shutting down daemon due to errors: Error loading docker apparmor profile: exec: "/sbin/apparmor_parser": stat /sbin/apparmor_parser: no such file or directory ()

Installing app-armor solves the problem.

[sameersbn]

@infinitydeveloper lets us know the suggestion by @thoriumbr helps.

[bitliner]

I already have installed apparmor, but still I get the same error. Kernel 3.13.0-85-generic

[pazoozooCH]

For me, I got that exception with the problem (and solution) outlined in https://github.com/docker/docker/issues/24155

[stale[bot]]

This issue has been automatically marked as stale because it has not had any activity for the last 60 days. It will be closed if no further activity occurs during the next 7 days. Thank you for your contributions.