docker.io requires apparmor but package does not depend on it

Bug #1309288 reported by stevenschlansker
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
docker.io (Ubuntu)
Fix Released
Medium
Unassigned
Trusty
Triaged
Medium
Unassigned
Utopic
Won't Fix
Medium
Unassigned

Bug Description

If you install ubuntu-minimal, apparmor is not installed.

If you then try to use docker, any attempt to launch one fails with:

root@ip-10-70-7-210:~# docker run busybox /bin/echo hi
2014/04/18 01:10:15 no such file or directory

once you:

root@ip-10-70-7-210:~# apt-get install apparmor apparmor-profiles

it then works:

root@ip-10-70-7-210:~# docker run busybox /bin/echo hi
2014/04/18 01:10:15 no such file or directory

This is tracked upstream as:

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

but seems to be un-resolved.

Tested on 14.04 LTS

Tags: trusty
Revision history for this message
Paul Tagliamonte (paultag) wrote :

What version of Docker do you have installed? I think this is fixed in 0.9.1, can you confirm?

https://github.com/dotcloud/docker/pull/4624 is the upstream fix, which made it in.

Changed in docker.io (Ubuntu):
status: New → Incomplete
importance: Undecided → High
Revision history for this message
stevenschlansker (stevenschlansker) wrote :

As the bug report says, this exists in the 14.04 release and still affects 0.9.1~dfsg1-2.

0.10.0 from upstream is also affected.

Changed in docker.io (Ubuntu):
status: Incomplete → New
Revision history for this message
Paul Tagliamonte (paultag) wrote :

OK. I'll mark it as triaged and see if I can work out a SRU fix.

Thanks!

Changed in docker.io (Ubuntu):
status: New → Triaged
Revision history for this message
Tianon Gravi (tianon) wrote :

Paul: we've got the dh_gencontrol stuff in our Git repo that adds apparmor to Recommends for Ubuntu - couldn't we at least start by backporting that one fix while the deps for a newer Docker version get sorted out (Bug #1338768)?

(For reference, it's commit 01e64d44435c3ce83c0914074f9851b8c875c41d that adds this: http://anonscm.debian.org/cgit/docker/docker.io.git/commit/?id=01e64d44435c3ce83c0914074f9851b8c875c41d)

This would need to be against our 0.9.1~dfsg1-2 release for now, right? If you think it'd be worthwhile, I'm happy to work up a branch for you to review that includes this fix and maybe any others we can make without our deps being bumped yet. Just say the word, boss! :)

Revision history for this message
James Page (james-page) wrote :

I don't see the apparmor on the 1.0.1 packaging, however the 1.2.0 that I've just test built does have this Dependency.

Changed in docker.io (Ubuntu Trusty):
importance: Undecided → Medium
Changed in docker.io (Ubuntu Utopic):
importance: High → Medium
Changed in docker.io (Ubuntu Trusty):
status: New → Confirmed
Changed in docker.io (Ubuntu Utopic):
status: Triaged → Confirmed
status: Confirmed → Triaged
Changed in docker.io (Ubuntu Trusty):
status: Confirmed → Triaged
Revision history for this message
Robie Basak (racb) wrote :

I see Recommends: apparmor and Depends: libapparmor1 in docker.io 1.5.0~dfsg1-1ubuntu2 that is in Wily, so I presume Fix Released?

For Trusty and Utopic, I expect this to be fixed by the planned backport of Wily's docker.io package to Trusty, Utopic and Vivid.

Changed in docker.io (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

utopic has seen the end of its life and is no longer receiving any updates. Marking the utopic task for this ticket as "Won't Fix".

Changed in docker.io (Ubuntu Utopic):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.