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.
Bug 2165875 - podman can not start a rootless container with option --privileged and runtime runc
Summary: podman can not start a rootless container with option --privileged and runtim...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Alex Jia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-31 10:42 UTC by Joy Pu
Modified: 2023-05-16 09:18 UTC (History)
10 users (show)

Fixed In Version: podman-4.4.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-16 08:23:27 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers podman pull 17301 0 None Merged [4.4] fix regression with runc --privileged rootless containers 2023-02-03 14:48:03 UTC
Red Hat Issue Tracker RHELPLAN-147015 0 None None None 2023-01-31 10:44:04 UTC
Red Hat Product Errata RHSA-2023:2758 0 None None None 2023-05-16 08:25:15 UTC

Description Joy Pu 2023-01-31 10:42:28 UTC
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:

Comment 1 Matthew Heon 2023-01-31 15:32:46 UTC
Giuseppe, can you take a look at this?

Comment 2 Giuseppe Scrivano 2023-01-31 16:15:18 UTC
PR here: https://github.com/containers/podman/pull/17301

Comment 6 Alex Jia 2023-02-13 06:40:41 UTC
This bug has been verified on podman-4.4.0-1.module+el8.8.0+18060+3f21f2cc.x86_64
with runc-1.1.4-1.module+el8.8.0+18060+3f21f2cc.x86_64.

[root@kvm-02-guest12 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.8 Beta (Ootpa)

[root@kvm-02-guest12 ~]# rpm -q podman runc systemd kernel
podman-4.4.0-1.module+el8.8.0+18060+3f21f2cc.x86_64
runc-1.1.4-1.module+el8.8.0+18060+3f21f2cc.x86_64
systemd-239-71.el8.x86_64
kernel-4.18.0-458.el8.x86_64

[root@kvm-02-guest12 ~]# 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
57c3046fbd4241239fc92a23f8e300fe763c9e2bced47a4c8cb7143d0324a201

[root@kvm-02-guest12 ~]# podman ps
CONTAINER ID  IMAGE                              COMMAND     CREATED         STATUS         PORTS       NAMES
57c3046fbd42  quay.io/libpod/testimage:20221018  top         11 seconds ago  Up 12 seconds              youthful_shamir

Comment 8 errata-xmlrpc 2023-05-16 08:23:27 UTC
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


Note You need to log in before you can comment on or make changes to this bug.