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

Can't push using service account key and docker-credentials-gcr #1154

Closed
tejal29 opened this issue Oct 21, 2021 · 4 comments
Closed

Can't push using service account key and docker-credentials-gcr #1154

tejal29 opened this issue Oct 21, 2021 · 4 comments

Comments

@tejal29
Copy link

tejal29 commented Oct 21, 2021

Hey folks,

I am trying to debug an issue in Kaniko GoogleContainerTools/kaniko#1786

I am trying the following steps

/workspace # /busybox/cat /kaniko/.docker/config.json 
{
	"auths": {},
	"credHelpers": {
		"gcr.io": "gcr"
	}
}
/workspace #  export GOOGLE_APPLICATION_CREDENTAILS=service_account.json

cat /kaniko/.config/gcloud/docker_credential_gcr_config.json 
{"TokenSources":["env"]}
/workspace # echo "gcr.io" | docker-credential-gcr get


docker-credential-gcr/helper: could not retrieve GCR's access token: oauth2: cannot fetch token: Post "https://oauth2.googleapis.com/token": dial tcp: lookup oauth2.googleapis.com: device or resource busy

I was able to get echo "gcr.io" | docker-credential-gcr get working before. Is there something missing in my flow?

@tejal29 tejal29 changed the title Can't push using service account key using docker-credentials-gcr Can't push using service account key and docker-credentials-gcr Oct 21, 2021
@mattmoor
Copy link
Collaborator

This doesn't look like a problem here 🤔

@imjasonh
Copy link
Collaborator

This seems like it might be related to GoogleContainerTools/kaniko#1631

I've never seen the device or resource busy error before, using ggcr or kaniko or anything else. Off the top of my head I don't think it's related to ggcr, but I'm willing to be convinced.

@tejal29
Copy link
Author

tejal29 commented Oct 25, 2021

hmm, I was able to use the above instructions before. Wondering what changed.

@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Keep fresh with the 'lifecycle/frozen' label.

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

No branches or pull requests

3 participants