You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/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?
The text was updated successfully, but these errors were encountered:
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-gcrOct 21, 2021
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.
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.
Hey folks,
I am trying to debug an issue in Kaniko GoogleContainerTools/kaniko#1786
I am trying the following steps
I was able to get
echo "gcr.io" | docker-credential-gcr get
working before. Is there something missing in my flow?The text was updated successfully, but these errors were encountered: