Skip to content
New issue

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

Setting Up a Job Step to Decode Credentials is confusing #1670

Closed
dhagge opened this issue Oct 13, 2017 · 2 comments · Fixed by #2142
Closed

Setting Up a Job Step to Decode Credentials is confusing #1670

dhagge opened this issue Oct 13, 2017 · 2 comments · Fixed by #2142
Assignees
Labels
unclear confusing language

Comments

@dhagge
Copy link

dhagge commented Oct 13, 2017

This issue is about https://circleci.com/docs/2.0/google-container-engine/ (source file: https://github.com/circleci/circleci-docs/blob/master/jekyll/_cci2/google-container-engine.md)

The section "Selecting a Base Image" references using google/cloud-sdk and the "Setting Up a Job Step to Decode Credentials" section references a custom docker container hosted out of the GCP container registry with auth username/password specified.

I found this quite confusing as in the example I changed - image: gcr.io/project/image-name to be - image: google/cloud-sdk which fails on build with the error Error response from daemon: Get https://registry-1.docker.io/v2/google/cloud-sdk/manifests/latest: unauthorized: incorrect username or password.

After some digging I figured out the issue was that specifying auth fails since google/cloud-sdk is a public docker image, but I think this should be drawn out better in the docs.

@aeneasr
Copy link
Contributor

aeneasr commented Oct 21, 2017

I stumbled on this as well! Thank you!

@ssinhas
Copy link

ssinhas commented Nov 21, 2017

I have the same issue. Documents is really vague and not very helpful.
Github links takes to repo which is nothing to do google cloud.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
unclear confusing language
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants