3. sudo docker run ubuntu:trusty uptime
2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied
What is expected? uptime to return something like:
$ sudo docker run ubuntu:trusty uptime
20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03
I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works.
Steps to reproduce (from https:/ /wiki.ubuntu. com/Process/ Merges/ TestPlans/ AppArmor):
1. sudo apt-get install docker.io # 1.2.0~dfsg1-1
2. sudo docker pull ubuntu:trusty
3. sudo docker run ubuntu:trusty uptime 455fb5e0bde9950 451152af1455688 0033818df7b50dd b1f4: set apparmor profile docker-default: permission denied
2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9
What is expected? uptime to return something like:
$ sudo docker run ubuntu:trusty uptime
20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03
I set 'sudo sysctl -w kernel. printk_ ratelimit= 0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works.