Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When we try to start a container with --privileged and runc under a non-root user. It will always report following error:
error creating device nodes: open /home/test/.local/share/containers/storage/overlay/cbbd26c3f79944ed80536efacb9bf4866df2dbf79c43827a774df7795329384a/merged/dev/tty: no such device or address
Version-Release number of selected component (if applicable):
podman-4.4.0-0.7.module+el8.8.0+17988+c6d0f56e.x86_64
runc-1.1.4-1.module+el8.8.0+17823+c4e3c815.x86_64
How reproducible:
100%
Steps to Reproduce:
1. start a non-root container with --privileged:
$ podman run --rm -d --privileged quay.io/libpod/testimage:20221018 top
Trying to pull quay.io/libpod/testimage:20221018...
Getting image source signatures
Copying blob a3ed95caeb02 done
Copying blob 578f06cc66c5 done
Copying config f5a99120db done
Writing manifest to image destination
Storing signatures
Resource limits are not supported and ignored on cgroups V1 rootless systems
Error: OCI runtime error: runc: runc create failed: unable to start container process: error during container init: error creating device nodes: open /home/test/.local/share/containers/storage/overlay/cbbd26c3f79944ed80536efacb9bf4866df2dbf79c43827a774df7795329384a/merged/dev/tty: no such device or address
Actual results:
The command exist with error message for create tty device
Expected results:
The command can finished as expected.
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: container-tools:rhel8 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:2758