Google Cloud Container Builder fails to push images to container registry

吃可爱长大的小学妹 提交于 2019-12-12 19:15:07

问题


My cloud builds used to push result images to GCR, but something happened and I am seeing this in my build logs:

PUSH
Pushing gcr.io/$PROJECT_ID/zookeeper:9c6def09508c52b9f364aa4751d520c79690e54c
The push refers to a repository [gcr.io/$PROJECT_ID/zookeeper]
174a611570d4: Preparing
f51f76255b02: Preparing
51db18d04d72: Preparing
f1c896f31e49: Preparing
0f5ff0cf6a1c: Preparing
0f5ff0cf6a1c: Layer already exists
f51f76255b02: Layer already exists
f1c896f31e49: Layer already exists
51db18d04d72: Layer already exists
174a611570d4: Layer already exists
name unknown: Buckets($PROJECT_ID,artifacts.$PROJECT_ID.appspot.com)

The above repeats for every layer. I'm not sure what happened. I recently revoked and re-logged-in with gcloud auth. But other gcloud commands work and gsutil works and shows that the above buckets exist. Permissions look good, but maybe I am missing something?

来源:https://stackoverflow.com/questions/47252697/google-cloud-container-builder-fails-to-push-images-to-container-registry

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!