Containerized AAP fails after SELinux relabeling on custom rootless storage path
Issue
After an administrator changes the rootless Podman storage location, or runs restorecon over a custom AAP storage path, AAP containers can fail to start or lose access to images, overlay data, or volumes.
Possible symptoms include:
- Podman commands fail with
permission denied. - AAP containers fail during creation or restart.
- Services cannot read or write container storage.
- SELinux AVC denials reference the AAP storage path.
Do not apply this procedure based only on a stopped container. Confirm SELinux evidence and the active Podman graphRoot first.
Environment
- Red Hat Ansible Automation Platform containerized installer
- Rootless Podman execution-plane services
- RHEL host with SELinux enabled and enforcing
- Custom execution-plane storage path, commonly configured through AAP's
~/aap/containers/storage.conf
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
