This repository has been archived by the owner on Oct 13, 2023. It is now read-only.
[18.03] Fix AppArmor not being applied to Exec processes #470
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cherry-pick of moby/moby#36466
No conflicts
fixes moby/moby#36456
Exec processes do not automatically inherit AppArmor profiles from the container.
This patch sets the AppArmor profile for the exec process.
Before this change:
Running
docker exec
doesn't get the profile applied:With this change:
Running
docker exec
gets the AppArmor profile applied- How to verify it
Build a
.deb
from this PR, using the Docker CE packaging scripts; https://github.com/docker/docker-ce-packaging/tree/master/debWhich puts the package in
debbuild/ubuntu-xenial
On an Ubuntu 16.04 machine, install the package:
Run the reproduction steps above
- Description for the changelog