Skip to content

apparmor: add signal and ptrace rules for stacked profiles#919

Open
bitoku wants to merge 1 commit into
podman-container-tools:mainfrom
bitoku:apparmor-stacking-fix
Open

apparmor: add signal and ptrace rules for stacked profiles#919
bitoku wants to merge 1 commit into
podman-container-tools:mainfrom
bitoku:apparmor-stacking-fix

Conversation

@bitoku

@bitoku bitoku commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

With AppArmor 5.0+, child processes get stacked profiles like profile//&crun. Add //&* wildcard rules for signal and ptrace to match stacked profile peers.

This is a reproducer.
https://gist.github.com/bitoku/6fe0dd11aed0e4dad31eb0171c49279f

This will fix cri-o/cri-o#10036 .

Assisted-by: Claude Code https://claude.com/claude-code

With AppArmor 5.0+ (Ubuntu 25.10+), child processes inside containers
get stacked profiles (e.g. containers-default//&crun). The existing
signal and ptrace peer rules only match the base profile name, causing
DENIED audit events that break systemd-based containers.

Add //&* wildcard rules for signal and ptrace to match any stacked
profile peer.

Signed-off-by: Ayato Tokubi <atokubi@redhat.com>
Assisted-by: Claude Code <https://claude.com/claude-code>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

common Related to "common" package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

On Ubuntu 26.04, systemd-based container fails to run systemd-journald.service in Kubernetes with CRI-O runtime

1 participant