google-container-registry

问题 I want to update my deployment on kubernetes with a new image which exists on 'eu.gcr.io' (same project), I have done this before. But now the pods fail to pull the image because they are not authorized to do so. This is the error that we get in the pod logs. Failed to pull image "eu.gcr.io/my-gcp-project/my-image:v1.009": rpc error: code = Unknown desc = Error response from daemon: unauthorized: You don't have the needed permissions to perform this operation, and you may have invalid

问题 I want to update my deployment on kubernetes with a new image which exists on 'eu.gcr.io' (same project), I have done this before. But now the pods fail to pull the image because they are not authorized to do so. This is the error that we get in the pod logs. Failed to pull image "eu.gcr.io/my-gcp-project/my-image:v1.009": rpc error: code = Unknown desc = Error response from daemon: unauthorized: You don't have the needed permissions to perform this operation, and you may have invalid

问题 Our container-builder fail to build an image we have that has a private git submodule command as part of the DockerFile. I linked the console account with the bitbucket account, (which has access to all repos) but still the build fail with "access denied" to the submodule repo. in Quay.IO builder i solved this by adding the ssh-key to the submodule repository, but since Container-Builder link with my account i can't use that solution. 回答1: Handling access to private submodules is a known

来源： https://stackoverflow.com/questions/46960446/push-to-google-container-registry-fails-retrying

来源： https://stackoverflow.com/questions/46960446/push-to-google-container-registry-fails-retrying

来源： https://stackoverflow.com/questions/46960446/push-to-google-container-registry-fails-retrying

问题 I am working on a bitbucket pipeline for pushing image to gc container registry. I have created a service account with Storage Admin role. (bitbucket-authorization@mgcp-xxxx.iam.gserviceaccount.com) gcloud auth activate-service-account --key-file key.json gcloud config set project mgcp-xxxx gcloud auth configure-docker --quiet docker push eu.gcr.io/mgcp-xxxx/image-name Although that the login is successful, i get: Token exchange failed for project 'mgcp-xxxx'. Caller does not have permission

问题 I'm hitting 429 error in Google Container Registry, too many images are pulled simultaneously Error: Status 429 trying to pull repository [...] "Quota Exceeded." There is a Kubernetes cluster with multiple nodes and pods implement Kubeflow steps. In the Google guide they suggest the following: To avoid hitting the fixed quota limit, you can: - Increase the number of IP addresses talking to Container Registry. Quotas are per IP address. - Add retries that introduce a delay. For example, you

问题 I'm hitting 429 error in Google Container Registry, too many images are pulled simultaneously Error: Status 429 trying to pull repository [...] "Quota Exceeded." There is a Kubernetes cluster with multiple nodes and pods implement Kubeflow steps. In the Google guide they suggest the following: To avoid hitting the fixed quota limit, you can: - Increase the number of IP addresses talking to Container Registry. Quotas are per IP address. - Add retries that introduce a delay. For example, you

问题 I'm having the sample problem as Vaclav. I've followed the GCR quick start to the letter which entailed creating a new project (called gcr-project) and copying the code for a Flask (python) app. After building the docker image, I entered the commands: gcloud auth configure-docker docker tag quickstart-image gcr.io/gcr-project/quickstart-image:tag1 docker push gcr.io/gcr-project/quickstart-image:tag1 The response was: unauthorized: You don't have the needed permissions to perform this