Unable to push to Google Cloud #1043

BenderV · 2018-06-28T12:50:10Z

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)

version: "3"
services:
  book-generator:
    image: gcr.io/xxx/book-generator:latest
    build: book-generator
    ports:
      - "5000:5000"

INFO Build key detected. Attempting to build and push image 'gcr.io/xxx/book-generator:latest'
INFO Building image 'gcr.io/xxx/book-generator:latest' from directory 'book-generator'
INFO Image 'gcr.io/xxx/book-generator:latest' from directory 'book-generator' built successfully
INFO Pushing image 'xxx/book-generator:latest' to registry 'gcr.io'
WARN Unable to retrieve .docker/config.json authentication details. Check that 'docker login' works successfully on the command line.: Failed to read authentication from dockercfg
INFO Authentication credentials are not detected. Will try push without authentication.
INFO Attempting authentication credentials 'gcr.io
ERRO Unable to push image 'xxx/book-generator:latest' to registry 'gcr.io'. Error: unauthorized: You don't have the needed permissions to perform this operation, and you may have invalid credentials. To authenticate your request, follow the steps in: https://cloud.google.com/container-registry/docs/advanced-authentication
FATA Error while deploying application: k.Transform failed: Unable to push Docker image for service book-generator: unable to push docker image(s). Check that `docker login` works successfully on the command line

~/.docker/config.json

{
  "auths": {
    "https://staging-k8s.gcr.io": {},
    "https://eu.gcr.io": {},
    "https://index.docker.io/v1/": {},
    "https://gcr.io": {},
    "staging-k8s.gcr.io": {},
    "asia.gcr.io": {},
    "gcr.io": {},
    "k8s.gcr.io": {},
    "us.gcr.io": {},
    "https://us.gcr.io": {},
    "https://k8s.gcr.io": {},
    "https://asia.gcr.io": {},
    "eu.gcr.io": {}
  },
  "credHelpers": {
    "gcr.io": "gcloud",
    "us.gcr.io": "gcloud",
    "eu.gcr.io": "gcloud",
    "asia.gcr.io": "gcloud",
    "staging-k8s.gcr.io": "gcloud"
  },
  "credsStore": "osxkeychain",
  "HttpHeaders": {
    "User-Agent": "Docker-Client/18.03.1-ce (darwin)"
  }
}

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 fine

Can you tell me how can I fix this issue ?

The text was updated successfully, but these errors were encountered:

Uelb · 2018-07-09T13:46:55Z

Have you read this conversation ? #911 it seems like it's the same issue

hangyan · 2018-07-10T05:07:39Z

@BenderV Does docker login and docker push works well?

BenderV · 2018-07-19T14:08:17Z

@hangyan yes, docker login and docker push works well.

lostcitizen · 2018-07-24T22:55:41Z

Similar thing happened to me.
I'm able to push with docker
docker push eu.gcr.io/XXXXXXX-####/container
but from "kompose up" just hangs on "INFO Attempting authentication credentials 'gcr.io "

keroloswilliam · 2018-09-03T20:48:54Z

had the same problem after running manually docker push and then tried kompose up again it worked for me

iancrowther · 2018-09-05T09:35:58Z

im also able to docker login and docker push.

> gcloud auth configure-docker
gcloud credential helpers already registered correctly.

ttelfer · 2018-10-03T18:20:41Z

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?

djmccormick · 2018-10-21T03:15:43Z

I tried this on macOS High Sierra and Ubuntu with the same results:

djmccormick at droplet in ~/Projects/foo on k8s
± kompose up
INFO Build key detected. Attempting to build and push image 'gcr.io/baz-foo/bar'
INFO Building image 'gcr.io/baz-foo/bar' from directory 'foo'
INFO Image 'gcr.io/baz-foo/bar' from directory 'foo' built successfully
INFO Pushing image 'baz-foo/bar:latest' to registry 'gcr.io'
WARN Unable to retrieve .docker/config.json authentication details. Check that 'docker login' works successfully on the command line.: Failed to read authentication from dockercfg
INFO Authentication credentials are not detected. Will try push without authentication.
INFO Attempting authentication credentials 'gcr.io
ERRO Unable to push image 'baz-foo/bar:latest' to registry 'gcr.io'. Error: unauthorized: You don't have the needed permissions to perform this operation, and you may have invalid credentials. To authenticate your request, follow the steps in: https://cloud.google.com/container-registry/docs/advanced-authentication
FATA Error while deploying application: k.Transform failed: Unable to push Docker image for service bar: unable to push docker image(s). Check that `docker login` works successfully on the command line

dmccormick at droplet in ~/Projects/foo on k8s
± docker push gcr.io/baz-foo/bar
The push refers to repository [gcr.io/baz-foo/bar]
f0d8f9de0422: Layer already exists
08b97a5a0452: Layer already exists
89099b8fb9c6: Layer already exists
c218274b2dd1: Layer already exists
df22d32922d6: Layer already exists
latest: digest: sha256:c74240eda4ae843ea88523c1ce2074f2be88ca9bbf21f1782dfc568490fc6d8f size: 1375

dmccormick at droplet in ~/Projects/foo on k8s
± docker login gcr.io
Authenticating with existing credentials...
Login Succeeded

dmccormick at droplet in ~/Projects/foo on k8s
± cat ~/.docker/config.json
{
	"auths": {
		"gcr.io": {}
	},
	"HttpHeaders": {
		"User-Agent": "Docker-Client/18.06.1-ce (linux)"
	},
	"credHelpers": {
		"asia.gcr.io": "gcloud",
		"eu.gcr.io": "gcloud",
		"gcr.io": "gcloud",
		"marketplace.gcr.io": "gcloud",
		"staging-k8s.gcr.io": "gcloud",
		"us.gcr.io": "gcloud"
	}
}%

wuestkamp · 2019-01-11T04:44:21Z

So I solved this on OSX by disabling the keychain password storage:

rm ~/.docker/config.json
in Docker for Mac preferences, untick "Securely store Docker logins in macOS keychain"
restart Docker for Mac
docker login

Or for glcoud and pushing to gcr:
gcloud auth print-access-token | docker login -u oauth2accesstoken --password-stdin https://eu.gcr.io

now your ~/.docker/config.json should contain base64 encoded passwords. Working, not safe though!

If someone gets the keychain storage to work that would be nice...

fejta-bot · 2019-04-11T05:30:52Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot · 2019-05-11T06:15:39Z

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

larssb · 2019-05-23T21:12:06Z

@wuestkamp manually update to the new version of Docker Compose. You can get it here. Follow the guideline for manually installing/updating it.
Even though the text says that you get the latest one if you are using Docker Desktop for Mac I did not have v1.24 of Docker Compose. Yes I did try checking for updates.

After having updated, when I execute e.g. docker-compose up --build I would get a more descriptive error. Suggesting me to actually execute gcloud auth login or set the creds with gcloud to the set I wanted to use.
After having done one of the two I was now able to execute the docker-compose cmd I wanted to.

I hope the above helps.

fejta-bot · 2019-06-22T22:00:13Z

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

k8s-ci-robot · 2019-06-22T22:00:20Z

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

xiuliren · 2019-10-06T20:12:18Z

I configured the docker to be used without sudo, and use docker push rather than sudo docker push
it works!

awmcclain · 2020-04-04T12:09:44Z

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.

Remove the credsStore key in ~/.docker/config.json

This will force docker to write the auth into the json when you use docker login. You can't untick Securely store Docker logins in macOS keychain in the docker desktop any more -- and the current credStore is no longer macOS keychain, it's desktop.

gcloud auth login Auth with gcloud (just to be explicit)
gcloud auth print-access-token | docker login -u oauth2accesstoken --password-stdin https://eu.gcr.io

You should see this:

WARNING! Your password will be stored unencrypted in /Users/andrew/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Login Succeeded

It would be super great to have Kompose use the credential helper properly!
/reopen

So I solved this on OSX by disabling the keychain password storage:

rm ~/.docker/config.json

in Docker for Mac preferences, untick "Securely store Docker logins in macOS keychain"

restart Docker for Mac

docker login

Or for glcoud and pushing to gcr:
gcloud auth print-access-token | docker login -u oauth2accesstoken --password-stdin https://eu.gcr.io

now your ~/.docker/config.json should contain base64 encoded passwords. Working, not safe though!

If someone gets the keychain storage to work that would be nice...

k8s-ci-robot · 2020-04-04T12:10:05Z

@awmcclain: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

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.

Remove the credsStore key in ~/.docker/config.json

This will force docker to write the auth into the json when you use docker login. You can't untick Securely store Docker logins in macOS keychain in the docker desktop any more -- and the current credStore is no longer macOS keychain, it's desktop.

gcloud auth print-access-token | docker login -u oauth2accesstoken --password-stdin https://eu.gcr.io

You should see this:
WARNING! Your password will be stored unencrypted in /Users/andrew/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Login Succeeded
It would be super great to have Kompose use the credential helper properly!
/reopen

So I solved this on OSX by disabling the keychain password storage:

rm ~/.docker/config.json

in Docker for Mac preferences, untick "Securely store Docker logins in macOS keychain"

restart Docker for Mac

docker login

Or for glcoud and pushing to gcr:
gcloud auth print-access-token | docker login -u oauth2accesstoken --password-stdin https://eu.gcr.io

now your ~/.docker/config.json should contain base64 encoded passwords. Working, not safe though!

If someone gets the keychain storage to work that would be nice...

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.

fejta-bot · 2020-05-06T14:40:26Z

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

k8s-ci-robot · 2020-05-06T14:40:41Z

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

imzahahs · 2020-06-29T16:00:43Z

So I solved this on OSX by disabling the keychain password storage:

rm ~/.docker/config.json

in Docker for Mac preferences, untick "Securely store Docker logins in macOS keychain"

restart Docker for Mac

docker login

Or for glcoud and pushing to gcr:
gcloud auth print-access-token | docker login -u oauth2accesstoken --password-stdin https://eu.gcr.io

now your ~/.docker/config.json should contain base64 encoded passwords. Working, not safe though!

If someone gets the keychain storage to work that would be nice...

Using gcloud auth print-access-token | docker login -u oauth2accesstoken --password-stdin https://eu.gcr.io worked for me instead of gcloud auth configure-docker in Jenkins with Ubuntu Slave

KrisLau · 2022-01-05T16:10:00Z

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.

Remove the credsStore key in ~/.docker/config.json

This will force docker to write the auth into the json when you use docker login. You can't untick Securely store Docker logins in macOS keychain in the docker desktop any more -- and the current credStore is no longer macOS keychain, it's desktop.

gcloud auth login Auth with gcloud (just to be explicit)

gcloud auth print-access-token | docker login -u oauth2accesstoken --password-stdin https://eu.gcr.io

You should see this:
WARNING! Your password will be stored unencrypted in /Users/andrew/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Login Succeeded
It would be super great to have Kompose use the credential helper properly! /reopen

@awmcclain Bless your soul I've been looking everywhere to fix this issue and this is the only thing that worked!

cdrage · 2022-01-12T14:07:28Z

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 kompose up or kompose down. Only supporting conversion to docker-compose.yaml files.

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 11, 2019

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 11, 2019

k8s-ci-robot closed this as completed Jun 22, 2019

hangyan reopened this Apr 6, 2020

k8s-ci-robot closed this as completed May 6, 2020

hangyan reopened this Jan 11, 2022

cdrage closed this as completed Jan 12, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unable to push to Google Cloud #1043

Unable to push to Google Cloud #1043

BenderV commented Jun 28, 2018

Uelb commented Jul 9, 2018

hangyan commented Jul 10, 2018

BenderV commented Jul 19, 2018

lostcitizen commented Jul 24, 2018 •

edited

Loading

keroloswilliam commented Sep 3, 2018

iancrowther commented Sep 5, 2018 •

edited

Loading

ttelfer commented Oct 3, 2018

djmccormick commented Oct 21, 2018

wuestkamp commented Jan 11, 2019 •

edited

Loading

fejta-bot commented Apr 11, 2019

fejta-bot commented May 11, 2019

larssb commented May 23, 2019

fejta-bot commented Jun 22, 2019

k8s-ci-robot commented Jun 22, 2019

xiuliren commented Oct 6, 2019

awmcclain commented Apr 4, 2020 •

edited

Loading

k8s-ci-robot commented Apr 4, 2020

fejta-bot commented May 6, 2020

k8s-ci-robot commented May 6, 2020

imzahahs commented Jun 29, 2020

KrisLau commented Jan 5, 2022 •

edited

Loading

cdrage commented Jan 12, 2022

Unable to push to Google Cloud #1043

Unable to push to Google Cloud #1043

Comments

BenderV commented Jun 28, 2018

Uelb commented Jul 9, 2018

hangyan commented Jul 10, 2018

BenderV commented Jul 19, 2018

lostcitizen commented Jul 24, 2018 • edited Loading

keroloswilliam commented Sep 3, 2018

iancrowther commented Sep 5, 2018 • edited Loading

ttelfer commented Oct 3, 2018

djmccormick commented Oct 21, 2018

wuestkamp commented Jan 11, 2019 • edited Loading

fejta-bot commented Apr 11, 2019

fejta-bot commented May 11, 2019

larssb commented May 23, 2019

fejta-bot commented Jun 22, 2019

k8s-ci-robot commented Jun 22, 2019

xiuliren commented Oct 6, 2019

awmcclain commented Apr 4, 2020 • edited Loading

k8s-ci-robot commented Apr 4, 2020

fejta-bot commented May 6, 2020

k8s-ci-robot commented May 6, 2020

imzahahs commented Jun 29, 2020

KrisLau commented Jan 5, 2022 • edited Loading

cdrage commented Jan 12, 2022

lostcitizen commented Jul 24, 2018 •

edited

Loading

iancrowther commented Sep 5, 2018 •

edited

Loading

wuestkamp commented Jan 11, 2019 •

edited

Loading

awmcclain commented Apr 4, 2020 •

edited

Loading

KrisLau commented Jan 5, 2022 •

edited

Loading