[RTFACT-17335] Artifactory in Docker cannot start with a custom user id Created: 16/Aug/18 Updated: 25/Mar/19 Resolved: 06/Dec/18
|Project:||Artifactory Binary Repository|
|Reporter:||Eldad Assis||Assignee:||Eldad Assis|
|Labels:||artifactory, docker, permissions|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Artifactory Docker with custom user id
MOTOROLA SOLUTIONS INC. - Support Case, Synopsys - Support Case, Charter Communications - Support Case, Registers of Scotland - Support Case, Arctiq Inc. - Support Case, IES - Support Case, Cigna - Support Case, BANK HAPOALIM - Support Case
|Internal Documentation:||docRelNotes, docWiki|
|Support Comments:|| This is quite urgent. An important customer experiencing regression.
(although they have workaround). The fix is ready, it would be great to push it to the next QA tests and upcoming release.
As an Artifactory in Docker deployer, I want to be able to set custom user and group ids to match existing user mappings on my system.
The new Artifactory (6.2.0) lost this ability due to permissions on the file system.
Fails with the following error:
NOTE - Artifactory entrypoint does start with user id 1717 and group id 1818, but the file system created during the docker build stage is assigned to the user id 1030 that was also created at build time.
|Comment by Eldad Assis [ 20/Aug/18 ]|
Until a solution is provided, the way to do this is to build a custom Docker image using our Dockerfile.
|Comment by Krzysztof Malinowski [ 20/Aug/18 ]|
While this is some kind of workaround, please note that it is not suitable in the long term. We have 3 sites, each running with a different user id, which means that the workaround requires creating 3 separate images.
|Comment by Eldad Assis [ 21/Aug/18 ]|
Yes Krzysztof Malinowski - we will provide a solution on our side. I added this comment as a temporary work around for you and others that might face similar issues.
|Comment by Alex Dvorkin [ 22/Nov/18 ]|
Konstantin Shenderov please wait until RTFACT-17881 is merged and re-do all the related testing. Sorry for the inconvenience.