GoogleCloudPlatform / GoogleCloudPlatform/docker-credential-gcr
Unable to use docker / docker-compose when auth fails
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 316
- Forks
- 94
- PR merge metrics
- No merged PRs in 30d
Description
If my password changes or there is a network issue and google-cloud-sdk/bin/docker-credential-gcr get fails you will be unable to run any commands locally using docker or docker-compose that have nothing to do with gcloud.
This is a massive pain, that my docker commands have been completely hijacked and if there is an issue with gcloud, then nothing works.
I would expect for it to try and do gcloud stuff, but upon failure let me do what I wanted any way.
It does my head in seeing [1249] Failed to execute script docker-compose for a totally gcloud independent task.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure around google-cloud-sdk/bin/docker-credential-gcr get while running an unrelated Docker or docker-compose command. Trace how the credential helper reports authentication or network failures, then verify that unrelated Docker commands can still run after that failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, go
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100