References to Docker Engine daemon(!) AppArmor Profile are misleading/incorrect and point to Docker CLI(!) AppArmor Profile
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- docker, linux
- Domain
- documentation, security
Research direction
Open engine/security/apparmor.md and review the two quoted paragraphs, then compare their paths and roles with contrib/apparmor and the referenced /etc/systemd/system/docker.service. Correct the CLI-versus-daemon wording and links so the documentation accurately identifies /usr/bin/docker and /usr/bin/dockerd.
Written by the indexing model from the issue text.
Description
File: engine/security/apparmor.md
A profile for the Docker Engine daemon exists but it is not currently installed with the deb packages. If you are interested in the source for the daemon profile, it is located in contrib/apparmor in the Docker Engine source repository.
This paragraph is incorrect: the apparmor profile linked to in contrib/apparmor defines a profile for /usr/bin/docker, which is the Docker CLI client. This is not the Docker engine daemon. Moreover, the repo directory linked to does not define any profile for /usr/bin/dockerd, the Docker engine daemon.
Advanced users and package managers can find a profile for
/usr/bin/docker(Docker Engine Daemon) underneath contrib/apparmor in the Docker Engine source repository.
This paragraph is incorrect: /usr/bin/docker is not the Docker engine daemon, it is the CLI client. The Docker engine daemon is /usr/bin/dockerd, as can be seen, for instance, from /etc/systemd/system/docker.service and many other places.
- Dominant language
- Markdown
- Stars
- 4.7k
- Forks
- 8.5k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 104
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
status/triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area/dhi status/triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100