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 1410841 - user namespace is not working
Summary: user namespace is not working
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: runc
Version: 7.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-06 15:41 UTC by Qian Cai
Modified: 2017-01-20 19:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-20 19:41:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Qian Cai 2017-01-06 15:41:25 UTC
Description of problem:
Setup user namespace is not working in runc.

# cat config.json
   "linux": {
        "uidMappings": [
                {
                        "hostID": 1000,
                        "containerID": 0,
                        "size": 32000
                }
        ],
        "gidMappings": [
                {
                        "hostID": 1000,
                        "containerID": 0,
                        "size": 32000
                }
        ],
...
    "process": {
        "args": [
            "touch",
            "root/foobar"
        ],
...
        "user": {}

# cat /proc/cmdline
... user_namespace.enable=1

# runc start root
could not synchronise with container process: operation not permitted

We might need to update to the latest upstream version which is working fine.

# /usr/local/sbin/runc -v
runc version 1.0.0-rc2
commit: 1a9dd2678d2d6ad574f05cb7b9ae46ce65586725
spec: 1.0.0-rc3

# /usr/local/sbin/runc create root
# /usr/local/sbin/runc start root
touch: cannot touch 'root/foobar': Permission denied

Version-Release number of selected component (if applicable):
runc-0.1.1-5.el7.x86_64

How reproducible:
always

Comment 1 Lokesh Mandvekar 2017-01-06 15:44:51 UTC
Can we delay this to 7.3.3?


Mrunal, do you know when runc 1.0.0 will be released?

Comment 3 Qian Cai 2017-01-20 19:41:30 UTC
This is working now as the rebase.


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