-
Notifications
You must be signed in to change notification settings - Fork 749
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
Unable to push to Google Cloud #1043
Comments
Have you read this conversation ? #911 it seems like it's the same issue |
@BenderV Does |
@hangyan yes, docker login and docker push works well. |
Similar thing happened to me. |
had the same problem after running manually |
im also able to
|
I am running into a similar issue but with Azure Container Registry. Both docker login and docker push work fine. Is it possible that its look for the .docker/config.json folder in the current directory rather than in the home directory ~/.docker/config.json? |
I tried this on macOS High Sierra and Ubuntu with the same results:
|
So I solved this on OSX by disabling the keychain password storage:
Or for glcoud and pushing to gcr: now your If someone gets the keychain storage to work that would be nice... |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@wuestkamp manually update to the new version of After having updated, when I execute e.g. I hope the above helps. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I configured the docker to be used without sudo, and use |
This is still an issue in Kompose for OSX and gcloud as of Docker Desktop 2.2.0.4. If you've done any googling on the topic, you'll see @wuestkamp's workaround, which needs a couple tweaks.
This will force docker to write the auth into the json when you use
You should see this:
It would be super great to have Kompose use the credential helper properly!
|
@awmcclain: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Using |
@awmcclain Bless your soul I've been looking everywhere to fix this issue and this is the only thing that worked! |
I'm going to close this for now as a NOTFIX because this is unrelated to Kompose and rather a Docker client issue. Kompose no longer supports |
I've tried every way to use Kompose, but I've always the same issue.
docker-compose.yml (with xxx being my google project name)
~/.docker/config.json
I tried every type of login but I've always the same error. What is really surprising is that a direct:
gcloud docker -- push gcr.io/xxx/book-generator:latest
works fineCan you tell me how can I fix this issue ?
The text was updated successfully, but these errors were encountered: