Docker 1.0.0 released and a bug dependent Apparmor_parser

June 10 Docker 1.0 Stable release, find an Ubuntu machine, installed the next

Ubuntu version:12.04

Docker version:1.0.0

The steps to install Docker can be seen in the official documentation: https://docs.docker.com/installation/ubuntulinux/

Once installed, run docker-d to try to start the Docker daemon with the following error:

[0fcb4ed6] +job serveapi (tcp://127.0.0.1:2375)[0fcb4ed6] +job Initserver () [0fcb4ed6.initserver ()] Creating server the/ ./ One Geneva: A: $Listening forHTTP on TCP (127.0.0.1:2375) [0fcb4ed6]+job Init_networkdriver () [0fcb4ed6]-job init_networkdriver () = OK (0) Error loading docker apparmor profile:exec:"/sbin/apparmor_parser":Stat/sbin/apparmor_parser:no suchfileor directory () [0FCB4ED6]-job initserver () = ERR (1) the/ ./ One Geneva: A: $Error loading docker AppArmor profile:exec:"/sbin/apparmor_parser":Stat/sbin/apparmor_parser:no suchfileor directory ()

On GitHub, someone had this problem a while ago:

https://github.com/dotcloud/docker/issues/4734

https://github.com/dotcloud/docker/issues/5114

Found that Docker could have been independent of apparmor_parser and tried to change the file/sys/module/apparmor/parameters/enabled

Change the original Y to N, note that the file defaults to Read-only

6 /sys/module/apparmor/parameters/echo N >/sys/module/apparmor/parameters/  chmod 4 /sys/module/apparmor/parameters/enabled

Then start docker-d &

Everything's fine.

PostScript: I do not know this apprmor_parser problem so solve whether there is a problem, or will bring other effects, the reader can directly comment on the blog, 3ks.