Many services fail to start in Containerised AAP installation due to memory protections

Solution Verified - Updated -

Issue

  • Installing AAP 2.5+ in containerised deployment under a user with home dir inside /var/lib directory
  • Running restorecon command to fix some files contexts
  • Since then, many AAP services (and containers) fail to start, logging errors with a shared library memory protection

Environment

Ansible Automation Platform (AAP) 2.5+

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content