Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This image creates
useras uid 1001. On a Linux host running Docker Engine, container ids are host ids, so for a host user with other ids, files written by the container on bind mounts belong to 1001. Adamant's activation also re-owns mounted repositories to 1001, and host git then refuses them.New
docker/entrypoint.shgivesuserthe uid and gid of whoever owns the mounted checkout, then runs the command asuser. It first removes any other image account or group with those ids, since Ubuntu's own account has 1000. This needs root, so the compose file starts the container as root, andadamant_env.sh startnow runs its first activation with-u user. A healthcheck reports ready once the ids are set, andstartwaits for it withup --wait.On Docker Desktop, a checkout reads as root's inside the container, so nothing changes there. GitHub workflows run the image directly, without the compose file, so CI is unaffected.