Skip to content

Add SUPERVISOR_UNCONFINED option and document AppArmor#172

Open
agners wants to merge 1 commit intomainfrom
add-environment-for-unconfined
Open

Add SUPERVISOR_UNCONFINED option and document AppArmor#172
agners wants to merge 1 commit intomainfrom
add-environment-for-unconfined

Conversation

@agners
Copy link
Copy Markdown
Member

@agners agners commented Apr 16, 2026

Allow users to opt out of AppArmor enforcement for the Supervisor by setting SUPERVISOR_UNCONFINED in their containerEnv. Document AppArmor behavior, host kernel considerations, and auditd limitations in the README.md.

Allow users to opt out of AppArmor enforcement for the Supervisor by
setting SUPERVISOR_UNCONFINED in their containerEnv. Document AppArmor
behavior, host kernel considerations, and auditd limitations in the
README.
Copy link
Copy Markdown
Contributor

@mdegat01 mdegat01 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So the code here looks fine and I expect it works without issue for the task at hand. However I can't test this locally because it seems I cannot use the run supervisor task at all. This is not due to your branch, the task does not work for me when I use the currently shipped image ghcr.io/home-assistant/devcontainer:5-supervisor either. I get this:

Run Supervisor
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Starting Supervisor
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Something else we changed here recently you think? I don't run this task much at all tbh so I don't have a good sense of how long ago this broke.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants