Update build to continue to work when moved to rootless jenkins #691
Conversation
This file contains 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
andytson-inviqa
force-pushed
the
feature/jenkins-rootless-fix
branch
2 times, most recently
from
0d9bb32 to
554b372
Compare
Jenkins runs docker agent nodes with --user uid:gid, so with the new runners being 1000:1000, they wont have root access in the container. Workspace image has a uid 1000 user and a 998 gid docker group set up to match the jenkins host. Technically only the 1000 uid user is needed to solve the missing home path. The docker group could just be the gid specified in other cases Any other images used as docker agent nodes without a 1000 uid user would either need to: * create that user * change HOME (or whatever other variable like COMPOSE_HOME) to either a /tmp folder or $WORKSPACE subdirectory
andytson-inviqa
force-pushed
the
feature/jenkins-rootless-fix
branch
from
554b372 to
0a8766f
Compare
kierenevans
approved these changes
May 6, 2022
andytson-inviqa
added
enhancement
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.
Jenkins runs docker agent nodes with --user uid:gid, so with the new runners being 1000:1000, they wont have root access in the container. Workspace image has a uid 1000 user and a 998 gid docker group set up to match the jenkins host.
Technically only the 1000 uid user is needed to solve the missing home path. The docker group could just be the gid specified in other cases
Any other images used as docker agent nodes without a 1000 uid user would either need to: