Adding workaround for git dubious owner#9
Open
topherbuckley wants to merge 1 commit into
Open
Conversation
topherbuckley
force-pushed
the
dubiousGitOwnerFix
branch
2 times, most recently
from
17196b3 to
2dcfa2e
Compare
topherbuckley
force-pushed
the
dubiousGitOwnerFix
branch
from
2dcfa2e to
b5cbdc6
Compare
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
1 participant
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.
Workaround for #8
Ideally the container user would assume the same UID:GID of the host user, but I couldn't get this to work, and adding it the
${docker_repo_path}was the simplest solution to overcoming the error. You may want to revisit this and apply a proper fix that doesn't do what I did, and essentially bypass the safety measures intended by git.