docker / docker/docs

References to Docker Engine daemon(!) AppArmor Profile are misleading/incorrect and point to Docker CLI(!) AppArmor Profile

Open Beginner friendly
#12,675 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/engine lifecycle/frozen
Dominant language
Markdown
Stars
4.7k
Forks
8.5k
Avg merge
2d 18h
Merged PRs (30d)
108

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
docker, linux
Domain
documentation, security
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.