We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When running the following locally:
sudo -E make docker
I get the following error:
docker run --rm \ --user 0:0 \ --env TARGET_GOOS= \ --env TARGET_GOARCH= \ --volume /tmp/amazon-ecr-credential-helper:/go/src/github.com/awslabs/amazon-ecr-credential-helper \ sha256:23b97de4f34d4c956e315659157439acfae03f15977d45c57c0e797729064846 \ make build git rev-parse --short=7 HEAD > GITCOMMIT_SHA fatal: detected dubious ownership in repository at '/go/src/github.com/awslabs/amazon-ecr-credential-helper' To add an exception for this directory, call: git config --global --add safe.directory /go/src/github.com/awslabs/amazon-ecr-credential-helper make: *** [Makefile:95: GITCOMMIT_SHA] Error 128
However running this seems to "fix" this problem.
docker run --rm \ --user 0:0 \ --env TARGET_GOOS= \ --env TARGET_GOARCH= \ --volume /tmp/amazon-ecr-credential-helper:/go/src/github.com/awslabs/amazon-ecr-credential-helper \ sha256:23b97de4f34d4c956e315659157439acfae03f15977d45c57c0e797729064846 \ git config --global --add safe.directory /go/src/github.com/awslabs/amazon-ecr-credential-helper && make build
I have also verified this behaviour on a CICD system.
However I do not see any docs / issues demonstrating this behaviour and it seems incorrect.
The text was updated successfully, but these errors were encountered:
Fix can be found here: #802
Sorry, something went wrong.
Thanks for opening and looking into this. Closing as resolved.
No branches or pull requests
When running the following locally:
I get the following error:
However running this seems to "fix" this problem.
I have also verified this behaviour on a CICD system.
However I do not see any docs / issues demonstrating this behaviour and it seems incorrect.
The text was updated successfully, but these errors were encountered: