Thanks!
That makes sense, and a welcome change to limit root access.
On Thu, Apr 16, 2020 at 2:46 PM Chris Lambertus wrote:
> Specifically, docker on the websites node (and ONLY the websites node) now
> uses userns-remap to the jenkins UID so you no longer need to pass a -u
> 910:910 parameter
Specifically, docker on the websites node (and ONLY the websites node) now uses
userns-remap to the jenkins UID so you no longer need to pass a -u 910:910
parameter to 'docker run’. Unfortunately, the nature of userns-remap means that
if you DO specify -u 910:910, things fail in a weird way. Sor
Hi,
Could you share what changes were made?
Beam is having issues since we use bind mounts to write output to the host.
Setting UID:GID on the image gives permission errors in the container when
accessing the mount (can't write).
Not setting it causes files to be created with the wrong (root:root
All,
Infra has implemented some permissions changes to the docker installation on
the websites node, and all containers now map to the jenkins UID on the host.
If you have specified a UID on the command line previously to avoid permissions
issues, your build may now be broken. Please remove any
