Why rootless podman container fails to start when "additionalimagestore" is used in Red Hat Enterprise Linux ?

Solution Verified - Updated -

Issue

  • Why does rootless podman container fail to start with "additionalimagestore" option ?
    • Path used in additionalimagestore is not owned by the rootless user and it is read-only
Error: OCI runtime error: runc: runc create failed: unable to start container process: error during container init: error mounting "tmpfs" to rootfs at "/tmp": tmpcopyup: failed to copy /tmp to /proc/self/fd/13 (/tmp/runctop3357647393/runctmpdir1069372518): open /proc/self/fd/13/: operation not supported

Environment

  • Red Hat Enterprise Linux 8.6
  • Podman 4.2
  • runc-1.1.3-3
  • fuse-overlayfs-1.9-1

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