-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins Core 2.73
When running a build inside a docker container, some commands don't work because they rely on the user being properly set. For example, ssh doesn't work with the following error:
No user exists for uid 150.
I think this could be solved by append to passwd on container startup, something like this (untested, for proof of concept):
if [ "$(id -u)" != "0" ]; then
echo "jenkins:x:$(id -u):$(id -g):Jenkins:${HOME}:/sbin/nologin" >> /etc/passwd
fi
- relates to
-
JENKINS-31944 Docker commandline passed wrong user id when executing.
-
- Closed
-
-
JENKINS-49416 Agent Dockerfile Overrides Entrypoint and User
-
- Open
-
I took the liberty to link issue JENKINS-49416 which is also a consequence of how is spinning Docker containers with an arbitrary user / group / entry point script.