You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Houston Putman (Jira)" <ji...@apache.org> on 2022/08/03 19:16:00 UTC

[jira] [Updated] (SOLR-16323) Use the User ID in the Dockerfile instead of the Username

     [ https://issues.apache.org/jira/browse/SOLR-16323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Houston Putman updated SOLR-16323:
----------------------------------
    Summary: Use the User ID in the Dockerfile instead of the Username  (was: Use the User GID in the Dockerfile instead of the Username)

> Use the User ID in the Dockerfile instead of the Username
> ---------------------------------------------------------
>
>                 Key: SOLR-16323
>                 URL: https://issues.apache.org/jira/browse/SOLR-16323
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Docker
>    Affects Versions: 9.0
>            Reporter: Houston Putman
>            Assignee: Houston Putman
>            Priority: Major
>
> There is a big trend towards using non-root Docker images. Luckily for us, Solr already uses a non-root user in its Docker image, solr:solr (8983:8983). However when specifying the "USER" at the end of the Dockerfile, it uses in the name instead of the ID. Therefore when certain security features are enabled, such as in Kubernetes, these tools cannot determine if the user "SOLR" is root or non-root. If we change to using the User ID, then these tools will begin to work.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org