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 1930552 - podman can not create user inside of container - regression introduced by fix for CVE-2021-20188
Summary: podman can not create user inside of container - regression introduced by fix...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: podman
Version: 7.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-19 06:51 UTC by Joy Pu
Modified: 2021-03-02 07:54 UTC (History)
8 users (show)

Fixed In Version: podman-1.6.4-29.el7_9 or newer
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-01 14:56:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Joy Pu 2021-02-19 06:51:33 UTC
Description of problem:
After fix https://bugzilla.redhat.com/show_bug.cgi?id=1918282, seems the permission inside container is not enough for create a new user correctly. The steps for setting up home directory always report Operation not permitted.

Version-Release number of selected component (if applicable):
podman-1.6.4-28.el7_9.x86_64 

How reproducible:
always

Steps to Reproduce:
1. Start a container
# podman run --name testctr -d docker.io/library/alpine:latest top
2. Use adduser to create a new user
# podman exec testctr adduser -S testuser
adduser: /home/testuser: Operation not permitted
adduser: /home/testuser: Operation not permitted
adduser: /home/testuser: Operation not permitted

3. Check the home directory
# podman exec -it testctr sh
/ # ls /home/ -l
total 0
drwxr-xr-x    2 root     root             6 Feb 19 06:38 testuser


Actual results:
adduser command failed to setup the home directory for new user


Expected results:
User can be created and used normally

Additional info:

Comment 21 Joy Pu 2021-02-23 17:34:09 UTC
Test with podman-1.6.4-29.el7_9.x86_64 and it works as expected now. So set this to verified.

Comment 23 errata-xmlrpc 2021-03-01 14:56:00 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 (Important: podman security 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-2021:0681


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