Unable to start container after changing selinux policy

Solution Verified - Updated -

Issue

  • Existing container do not start post reboot after changing selinux policy.
  • Unable to start container due to error failed to mount shm tmpfs.

Environment

  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9

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