google-container-registry

GKE - ErrImagePull pulling from Google Container Registry

倖福魔咒の 提交于 2019-12-02 00:57:18
问题 I have a Google Kubernetes Engine cluster which until recently was happily pulling private container images from a Google Container Registry bucket. I haven't changed anything, but now when I update my Kubernetes Deployments, it's unable to launch new pods, and I get the following events: Normal Pulling 14s kubelet, <node-id> pulling image "gcr.io/cloudsql-docker/gce-proxy:latest" Normal Pulling 14s kubelet, <node-id> pulling image "gcr.io/<project-id>/backend:62d634e" Warning Failed 14s

gcloud docker push reliability

£可爱£侵袭症+ 提交于 2019-12-01 19:03:08
问题 I have been having a lot of problems pushing images with gcloud docker push over the past few weeks. I've read through the many stack overflow discussions and github issues and workarounds but I haven't come across a solution to the inconsistency yet. Typically I will attempt to push a container image or two. The first push will almost always fail with the following retry-until-timeout output: I can only get around it with gcloud auth login . At most 5 minutes later I will attempt to push a

gcloud docker push 403 Forbidden

孤街醉人 提交于 2019-12-01 17:40:13
I am trying to push a docker image to eu.gcr.io and I am getting 403 Forbidden gcloud docker push eu.gcr.io/<projectname>/<image>:latest The push refers to a repository [eu.gcr.io/<projectname>/<image>] (len: 1) 663cd9de01fe: Preparing Post https://eu.gcr.io/v2/w<projectname>/<image>/blobs/uploads/: token auth attempt for registry: https://eu.gcr.io/v2/token?account=_token&scope=repository%3A<projectname>%2F<image>3Apush%2Cpull&service=eu.gcr.io request failed with status: 403 Forbidden I have checked curl https://eu.gcr.io/v1/_ping => works gcloud config list => project id is setup Storage

gcloud docker push 403 Forbidden

故事扮演 提交于 2019-12-01 17:31:03
问题 I am trying to push a docker image to eu.gcr.io and I am getting 403 Forbidden gcloud docker push eu.gcr.io/<projectname>/<image>:latest The push refers to a repository [eu.gcr.io/<projectname>/<image>] (len: 1) 663cd9de01fe: Preparing Post https://eu.gcr.io/v2/w<projectname>/<image>/blobs/uploads/: token auth attempt for registry: https://eu.gcr.io/v2/token?account=_token&scope=repository%3A<projectname>%2F<image>3Apush%2Cpull&service=eu.gcr.io request failed with status: 403 Forbidden I

How to remove a pushed image in Google Container Registry

社会主义新天地 提交于 2019-11-30 17:20:45
Is it possible to remove a pushed image from Google Container Registry ? I mean without handling the Google Cloud Storage directory directly. Thanks! Franck As explained here you can delete an image from Google Container Registry with the following gcloud command: gcloud container images delete IMAGE_NAMES [IMAGE_NAMES …] [GLOBAL-FLAG …] With current UI and its implementation, you can only delete tags, the underlying images will not be deleted. If it is a Docker V2 images, from command line you can delete the image using Docker Registry API , by deleting the tags first, and then deleting the

`docker-credential-gcloud` not in system PATH

ぐ巨炮叔叔 提交于 2019-11-30 10:49:41
After the latest updates to gcloud and docker I'm unable to access images on my google container repository. Locally when I run: gcloud auth configure-docker as per the instructions after updating gcloud, I get the following message: WARNING: `docker-credential-gcloud` not in system PATH. gcloud's Docker credential helper can be configured but it will not work until this is corrected. gcloud credential helpers already registered correctly. Running which docker-credential-gcloud returns docker-credential-gcloud not found . I have no other gcloud-related path issues and for the life of me can't

Creating image pull secret for google container registry that doesn't expire?

点点圈 提交于 2019-11-30 08:27:41
I'm trying to get Kubernetes to download images from a Google Container Registry from another project. According to the docs you should create an image pull secret using: $ kubectl create secret docker-registry myregistrykey --docker-server=DOCKER_REGISTRY_SERVER --docker-username=DOCKER_USER --docker-password=DOCKER_PASSWORD --docker-email=DOCKER_EMAIL But I wonder what DOCKER_USER and DOCKER_PASSWORD I should use for authenticating with Google Container Registry? Looking at the GCR docs it says that the password is the access token that you can get by running: $ gcloud auth print-access

Pull private docker images from Google Container Registry w/o gcloud

这一生的挚爱 提交于 2019-11-30 05:06:21
I'm using shippable to push private docker images to the Google Container Registry that I then want to pull from either locally on a laptop, or inside an instance on the Google Compute Engine. I know that the command gcloud preview docker pull gcr.io/projectID/image-name works, but I can't rely on gcloud being installed on every machine that someone may need to pull the image from. If I run docker-compose up -d on my machine then I get the following error: Pulling image gcr.io/projectID/image-name... Pulling repository gcr.io/projectID/image-name Traceback (most recent call last): File "

How do I run private docker images on Google Container Engine

旧时模样 提交于 2019-11-29 20:20:48
How do I run a docker image that I built locally on Google Container Engine ? proppy You can push your image to Google Container Registry and reference them from your pod manifest. Detailed instructions Assuming you have a DOCKER_HOST properly setup , a GKE cluster running the last version of Kubernetes and Google Cloud SDK installed. Setup some environment variables gcloud components update kubectl gcloud config set project <your-project> gcloud config set compute/zone <your-cluster-zone> gcloud config set container/cluster <your-cluster-name> gcloud container clusters get-credentials <your

Creating image pull secret for google container registry that doesn't expire?

风格不统一 提交于 2019-11-29 11:45:05
问题 I'm trying to get Kubernetes to download images from a Google Container Registry from another project. According to the docs you should create an image pull secret using: $ kubectl create secret docker-registry myregistrykey --docker-server=DOCKER_REGISTRY_SERVER --docker-username=DOCKER_USER --docker-password=DOCKER_PASSWORD --docker-email=DOCKER_EMAIL But I wonder what DOCKER_USER and DOCKER_PASSWORD I should use for authenticating with Google Container Registry? Looking at the GCR docs it