This bug was fixed in the package linux - 3.18.0-8.9
---
linux (3.18.0-8.9) vivid; urgency=low
[ Leann Ogasawara ]
* Release Tracking Bug
- LP: #1407692
* rebase to v3.18.1
* ubuntu: AUFS -- Resolve build failure union has no member named
'd_child'
[ Upstream Kerne
** Also affects: apparmor (Ubuntu Vivid)
Importance: High
Status: Invalid
** Also affects: linux (Ubuntu Vivid)
Importance: High
Assignee: John Johansen (jjohansen)
Status: Fix Released
** Also affects: docker.io (Ubuntu Vivid)
Importance: High
Status: Invalid
I just found that the apparmor profile for docker was disabled for some
reason. After removing the symlink from /etc/apparmor.d/disable/docker,
it works. I don't remember ever adding docker to the apparmor disable
links.
--
You received this bug notification because you are a member of Ubuntu
Bug
I also tried the 3.17.0-031700-generic #2001410060605 linked above. It
also does not work on that kernel.
# docker run -i -t ubuntu /bin/bash
Unable to find image 'ubuntu' locally
Pulling repository ubuntu
1357f421be38: Download complete
511136ea3c5a: Download complete
1de2bd7201a2: Download com
Just so you know, here's the docker.io package version also:
ii docker.io 1.2.0~dfsg1-1ubuntu1 amd64Linux container runtime
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371310
Title:
I am getting the following still.
# docker run -i -t ubuntu /bin/bash
set apparmor profile docker-default: no such file or directory2014/10/13
11:05:41 Error response from daemon: Cannot start container
7981801146ab1771470fd72bc97e6582ff573fa159199f6cb86afaa7eaa74ea9: set apparmor
profile docker
Yep, Docker works again with kernel 3.16.0-22.29. Thanks for fixing this
so promptly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371310
Title:
docker.io doesn't work with apparmor 3.0 RC1 kernel
This bug was fixed in the package linux - 3.16.0-22.29
---
linux (3.16.0-22.29) utopic; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1379321
[ Andrew Morton ]
* SAUCE: (no-up) mm-introduce-a-general-rcu-get_user_pages_fast-fix
- LP: #1309221
* SAUCE:
Workaroud: Updating to kernel 3.17 ( from here: http://kernel.ubuntu.com
/~kernel-ppa/mainline/v3.17-utopic/ ) solves this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371310
Title:
docker.io doe
FYI, this should be in a new kernel soon:
https://lists.ubuntu.com/archives/kernel-team/2014-October/049001.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371310
Title:
docker.io doesn't work w
I can confirm that reverting the patch John Johansen mentioned makes
docker.io work as well as in previous releases. We will have this fixed
before 14.10 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-14.10
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371310
Title:
do
@jdstrand:
Sorry, I missed that bit. I rebooted into the old Trusty kernel and
Docker works fine (although compiz/mesa don't like the old kernel, so I
guess I'll try 3.16.0-16.22). Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
John, from the description: "Workaround until this bug is fixed is to
boot into 3.16.0-16.22 or earlier." If you upgraded, you probably still
have the trusty kernel installed, so you can boot into that. Otherwise,
use https://launchpad.net/ubuntu/utopic/+source/linux/3.16.0-16.22
--
You received
I just upgraded to Utopic final beta and am experiencing this bug. What
is a workaround to get my docker containers working?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371310
Title:
docker.io do
d'oh, lost context on this thread and thought it was a new bug against
docker with a patch. my fault. carry on, thanks folks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371310
Title:
docker.io d
I'll take a look at adding this to Debian & Ubuntu - can we get this
upstreamed too?
On Tue, Sep 23, 2014 at 3:01 PM, Jamie Strandboge wrote:
> ** Tags added: apparmor
>
> --
> You received this bug notification because you are a member of Docker
> Ubuntu Maintainers, which is subscribed to docke
** Tags added: apparmor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371310
Title:
docker.io doesn't work with apparmor 3.0 RC1 kernel
To manage notifications about this bug go to:
https://bugs.l
Specifically we will revert the patch to security/apparmor/domain.c
fix: only allow a single threaded process to change context on exec
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371310
Title:
** Description changed:
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
2014/09/18 15:48:48 Error response from daem
20 matches
Mail list logo
