Closed Kalmalyzer closed 3 years ago
Non-Docker Linux runs using a jenkins
account with a nondeterministic UID. Non-Docker Win64 has a jenkins
account on the VM, and a Jenkins
account within the VM as well.
This concerns specifically the cases where we run Docker Linux on VMs. We probably should move away from the COS + cloud-init strategy, but then we need to understand how to handle UIDs better.
The Docker (non-Kubernetes) agents have been retired. They didn't add much and were generally more troublesome when something went wrong.
Closing this as won't fix.
Today, the Swarm & Inbound agents run as UID=1000, This happens to be a preexisting account in COS. It would be cleaner if those could run with the UID of the
jenkins-ssh
account. Is the Jenkins container compatible with arbitrary UIDs/GIDs? Is the buildtools container compatible with arbitrary UIDs/GIDs?