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:

The docker service does not have a uniform / set UID/GID like other services. 

How reproducible: 100% 

Steps to Reproduce:
1. Install docker

Actual results:

A UID / GID is set based on what is avalabe at the time of the RPM install. 

Expected results:

The UID/GID should be consistant as it is with other services out of /usr/share/doc/setup/uidgid

Additional info:

# grep docker /etc/passwd
dockerroot:x:997:995:Docker User:/var/lib/docker:/sbin/nologin

# rpm -q docker --scripts
preinstall scriptlet (using /bin/sh):
getent passwd dockerroot > /dev/null || /usr/sbin/useradd -r -d /var/lib/docker -s /sbin/nologin -c "Docker User" dockerroot
...

How does one go about assigning a persistant UID for docker?

Er, no.  Not every RPM gets a fixed uid, it simply would not scale.

If you're using RPMs-assembled-on-client (e.g. yum) you can simply `useradd` before installing the RPM and choose whatever name -> uid mappings you desire.

If you're using Atomic Host, this is done for you.

Great Colin, thanks, did not know that info.

Currently the dockerroot user is not used by anything other then locally on the system to separate root user within the container from root user on the host.  Theoretically this should never leave the host,  but I guess could if you were using shared volumes into containers which you wanted owned by dockerroot.

Eric any movement on this?

(In reply to Daniel Walsh from comment #8)
> Eric any movement on this?

Dan I'm confused on the question. The bug was re-opened, given that we have an inconsistency with products that do and do not set UID/GID values for services. 

Does engineering have any objections to setting a default value for the UID/GID for docker?

I agree with Colin that there is no need to make this consistent across docker instances. we are not currently sharing it over shared network storage. So I am closing this as wontfix.