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

Docker fails to start some containers on Ubuntu 14.04 boot (apparmor) #5788

Closed
fermayo opened this Issue May 14, 2014 · 5 comments

Comments

Projects
None yet
9 participants
@fermayo
Contributor

fermayo commented May 14, 2014

When docker is configured with --restart=true on an Ubuntu 14.04 machine, and the host is restarted, some containers fail to start on boot with the following message in the logs:

set apparmor profile docker-default: no such file or directory

However, they run fine when doing docker start afterwards.

Maybe a race condition between docker and apparmor on boot?

docker info:

Containers: 1
Images: 15
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Dirs: 17
Execution Driver: native-0.2
Kernel Version: 3.13.0-24-generic

docker version:

Client version: 0.11.1
Client API version: 1.11
Go version (client): go1.2.1
Git commit (client): fb99f99
Server version: 0.11.1
Server API version: 1.11
Git commit (server): fb99f99
Go version (server): go1.2.1
Last stable version: 0.11.1

uname -a

Linux trusty64 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
@lapluviosilla

This comment has been minimized.

Show comment
Hide comment
@lapluviosilla

lapluviosilla May 14, 2014

I have this exact same issue. I also have the latest version of docker and I'm using trusty64. I also tried disabling and removing apparmor and setting it to complain mode.

lapluviosilla commented May 14, 2014

I have this exact same issue. I also have the latest version of docker and I'm using trusty64. I also tried disabling and removing apparmor and setting it to complain mode.

@adamsdarlingtower

This comment has been minimized.

Show comment
Hide comment
@adamsdarlingtower

adamsdarlingtower May 20, 2014

We've been getting this error on some host machines but not others. All of our host machines are running ubuntu 12.04 . It happens on docker build, and on docker run. A reboot of the host sometimes fixes it.

adamsdarlingtower commented May 20, 2014

We've been getting this error on some host machines but not others. All of our host machines are running ubuntu 12.04 . It happens on docker build, and on docker run. A reboot of the host sometimes fixes it.

@Romain-Geissler

This comment has been minimized.

Show comment
Hide comment
@Romain-Geissler

Romain-Geissler May 26, 2014

My understanding of the issue is that apparmor must have loaded the docker configuration before docker tries to run containers. I don't know whuch program should do this (I guess it's the init program). In such case, you must ensure that init configures apparmor correctly before running the docker deamon.
There is another issue, when you try to run Ubuntu 12.04 with the 14.04 kernel. Oldest version of apparmor cannot load the docker profile: /lib/init/apparmor-profile-load docker might log "Feature buffer full". This will block any docker run command. In that case, updating the "apparmor" package will solve the issue.

Romain-Geissler commented May 26, 2014

My understanding of the issue is that apparmor must have loaded the docker configuration before docker tries to run containers. I don't know whuch program should do this (I guess it's the init program). In such case, you must ensure that init configures apparmor correctly before running the docker deamon.
There is another issue, when you try to run Ubuntu 12.04 with the 14.04 kernel. Oldest version of apparmor cannot load the docker profile: /lib/init/apparmor-profile-load docker might log "Feature buffer full". This will block any docker run command. In that case, updating the "apparmor" package will solve the issue.

@mikedanese

This comment has been minimized.

Show comment
Hide comment
@mikedanese

mikedanese Oct 9, 2014

Contributor

Still getting this issue I think

Linux kafkatest00.dev 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Containers: 2
Images: 78
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Dirs: 82
Execution Driver: native-0.2
Kernel Version: 3.13.0-24-generic
Operating System: Ubuntu 14.04 LTS
WARNING: No swap limit support

any fix?

Contributor

mikedanese commented Oct 9, 2014

Still getting this issue I think

Linux kafkatest00.dev 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Containers: 2
Images: 78
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Dirs: 82
Execution Driver: native-0.2
Kernel Version: 3.13.0-24-generic
Operating System: Ubuntu 14.04 LTS
WARNING: No swap limit support

any fix?

@schmunk42

This comment has been minimized.

Show comment
Hide comment
@schmunk42

schmunk42 Mar 28, 2015

Contributor

I had an issue with docker-composer and wrong volume syntax, see also http://stackoverflow.com/a/28750998/291573

Contributor

schmunk42 commented Mar 28, 2015

I had an issue with docker-composer and wrong volume syntax, see also http://stackoverflow.com/a/28750998/291573

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