Skip to content

About

Docker build images for GitVersion

Topics

Resources

Stars

11 stars

Watchers

2 watching

Forks

Latest commit

 

History

399 Commits

Folders and files

Repository files navigation

build-images

Quality Gate Status Reliability Rating Security Rating Maintainability Rating

Docker build images for GitVersion & LibGit2Sharp

Container user policy

All six Linux dependency images and their SDK/runtime derivatives default to the gittools user, UID/GID 10001:10001, with home /home/gittools. Root is used only during image assembly to install OS packages and .NET into /usr/local/bin. Generated Dockerfiles restore USER 10001:10001 after installation. The build checks the default UID before publishing each image.

Downstream Dockerfiles that install into system-owned paths must explicitly switch to root for those build steps and restore a non-root final user. GitVersion's corresponding changes are tracked in GitTools/GitVersion#5207. Validate that consumer before merging this change: an earlier non-root setup was reverted in 1c848852f342223a523659a7451f762988a3f43b after downstream failures.

Bind-mounted repositories must be writable by the container user when tools update Git state or generate build outputs. On Linux, run as the non-root checkout owner with --user "$(id -u):$(id -g)"; if that UID differs from 10001, also supply a writable container-local home, for example --env HOME=/tmp --env DOTNET_CLI_HOME=/tmp. Do not make the checkout world-writable or recursively change its ownership.

The GitVersion Docker and artifact test matrix must pass across both architectures, supported distros, .NET versions, and Git backends before rollout. Sonar's previously accepted root-user findings must be re-evaluated after analysis of these changes; the earlier exception does not count as verification of the non-root implementation.

About

Docker build images for GitVersion

Topics

Resources

Stars

11 stars

Watchers

2 watching

Forks

Releases

Packages

Used by

Contributors

Languages