Skip to content

docs(apparmor): add warning about profile persistence#23381

Closed
texhnolyze wants to merge 1 commit into
docker:mainfrom
texhnolyze:patch-1
Closed

docs(apparmor): add warning about profile persistence#23381
texhnolyze wants to merge 1 commit into
docker:mainfrom
texhnolyze:patch-1

Conversation

@texhnolyze
Copy link
Copy Markdown

across reboots, as /etc/apparmor.d/containers will not be loaded, leading to the example nginx container not being able to start.

Description

Following the example to set up a custom apparmor profile.
I was suprised, that the profile suggested being located in /etc/apparmor.d/containers was not automatically loaded after a reboot.
This is because apparmor only loads files directly located in /etc/apparmor.d/* or known folder locations according to the Policy Layout.

This led to my container not being able to start with error:

Failed starting container: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: unable to apply apparmor profile: apparmor failed to apply profile: write /proc/thread-self/attr/apparmor/exec: no such file or directory: unknown

For this reason, I've added a warning section in the docs.

Reviews

  • Technical review
  • Editorial review
  • Product review

@github-actions github-actions Bot added area/engine Issue affects Docker engine/daemon area/security labels Sep 9, 2025
@netlify
Copy link
Copy Markdown

netlify Bot commented Sep 9, 2025

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 70f2b53
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/68c6d389a777f800080baa18
😎 Deploy Preview https://deploy-preview-23381--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

across reboots, as `/etc/apparmor.d/containers` will not be loaded, leading to the example `nginx` container not being able to start.
@github-actions
Copy link
Copy Markdown
Contributor

Thanks for the PR. We'd like to make our product docs better, but haven't been able to review all the suggestions. As our docs change often and quickly diverge, we do not have the bandwidth to review and rebase old PRs.

If the updates are still relevant, please add a comment and review our contribution guidelines to rebase your PR against the latest version of the docs. This helps our maintainers focus on active contributions. If there's no activity, this PR will be closed in 30 days.

To remove the stale label: Comment /lifecycle active
To freeze (requires write access): Comment /lifecycle frozen

@github-actions
Copy link
Copy Markdown
Contributor

Closing this PR as there hasn't been any activity for a long time.

If the updates are still relevant, please review our contribution guidelines and create a new PR against the latest version of our docs.

@github-actions github-actions Bot closed this May 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/engine Issue affects Docker engine/daemon area/security lifecycle/stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant