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 running the rhel-tools container on OpenShift
> oc run --restart=Never --attach --stdin --tty --image registry.access.redhat.com/rhel7/rhel-tools rhel-tools bash> oc run --generator=deploymentconfig/v1 --attach --stdin --tty --image registry.access.redhat.com/rhel7/rhel-tools rhel-tools bash
Version-Release number of selected component (if applicable): "Id": "a94093b96828a0964d8d0147d96984547e24a080cbeac14d976ff5431495de46"
How reproducible: 100%
Steps to Reproduce:
1. oc run --restart=Never --attach --stdin --tty --image registry.access.redhat.com/rhel7/rhel-tools rhel-tools bash
2: oc whoami
Actual results:
User is not known.
Expected results:
The user should be known or "faked"
Additional info:
https://docs.openshift.com/enterprise/3.2/creating_images/guidelines.html#openshift-enterprise-specific-guidelines
Isn't this really a docker issue, that if you run as a specified UID and the UID is not defined in the /etc/passwd inside of the container, it can not translate it?
Comment 3Frantisek Kluknavsky
2016-10-05 10:54:33 UTC
I would really rather not add nss_wrapper to RHEL just for a short-term workaround for what is (in this case) a mostly-cosmetic issue. It's a genuine issue, but the rhel-tools case doesn't seem a strong reason for adding it here.
So the real question is whether this is the long-term answer we want for this general problem.
(In reply to Daniel Walsh from comment #2)
> Isn't this really a docker issue, that if you run as a specified UID and the
> UID is not defined in the /etc/passwd inside of the container, it can not
> translate it?
Right, it feels like we need some core plumbing to deal with this, and not just hack around it in the container image. User namespaces may help, but is likely insufficient on its own.
Dan, do we have a plan for handling this sort of thing more cleanly?
Comment 7Frantisek Kluknavsky
2018-04-19 13:49:38 UTC
Bugzilla to add nss_wrapper to rhel is still not solved. Meanwhile, development of user namespaces moved a lot. I guess this bugzilla is obsolete. Feel free to reopen if you disagree.