apparmor="DENIED" on docker container files
Bug #1880025 reported by
Jan Berghoff-Flüel
This bug report is a duplicate of:
Bug #1879690: Docker registry doesn't stay up and keeps restarting.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
% docker run -it ubuntu bash
yields:
kernel: audit: type=1400 audit(159007166
profile=
denied_mask="r" fsuid=0 ouid=0
with:
vmlinuz-
Nearly all containers cannot start properly and hence malfunction.
With vmlinuz-
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
Thank you for filing a bug, but this is not a bug for the AppArmor project. It sounds like it might be a bug against the docker snap. This looks similar to docker not transitioning the container into the container profile. I'm tentatively going to assign this to the snapd project since a snapd developer may be able to advise on how to fix the docker snap.