google-container-registry

EDIT: I'm just going to blame this on platform inconsistencies. I have given up on pushing to the Google Cloud Container Registry for now, and have created an Ubuntu VM where I'm doing it instead. I have voted to close this question as well, for the reasons stated previously, and also as this should probably have been asked on Server Fault in the first place. Thanks for everyone's help! running $ gcloud docker push gcr.io/kubernetes-test-1367/myapp results in: The push refers to a repository [gcr.io/kubernetes-test-1367/myapp] 595e622f9b8f: Preparing 219bf89d98c1: Preparing 53cad0e0f952:

I have pushed container images using gcloud docker push to the Google Container Registry. Two questions: How do I cleanly remove a pushed container image from the registry? (I know I can remove a tag to an image and make it not accessible anymore.) There are a bunch of Docker layers that an image brings with it. I want to remove all the unused layers with an image deletion. Sandeep Dinesh UPDATE: You can now delete individual container images straight from the UI. Go to the Container Registry page . You should see a list of container images. Click the one you want to delete. Select one or more

Whenever I attempt to push a container to the Google Container Registry from my local machine, I get the following error: denied: Unable to access the repository; please check that you have permission to access it. If I open the Cloud Shell, I can push containers with no problems. I have tried doing "gcloud auth login" several times and it seems to make no difference. I don't have any problems running other gcloud commands locally. Any help would be greatly appreciated. FYI for other customers running into similar issues: https://github.com/docker/docker/issues/22910 There exists a bug with

Is there a gcloud API or other command line interface (CLI) to access the list of published container images in the private Google Container Registry? (That is the container registry inside a Google Cloud Platform project) gcloud container does not seem to help: $ gcloud container Usage: gcloud container [optional flags] <group | command> group may be clusters | operations command may be get-server-config Deploy and manage clusters of machines for running containers. flags: --zone ZONE, -z ZONE The compute zone (e.g. us-central1-a) for the cluster global flags: Run `gcloud -h` for a

Using the Container Optimized OS (COS) on Google Cloud Compute, what's the best way to access the credentials of the default service account for the VM-project from within a Docker container? $ gcloud compute instances create test-instance \ --image=cos-stable --image-project=cos-cloud $ ssh (ip of the above) # gcloud ... Command not found # docker run -ti google/cloud-sdk:alpine /bin/sh # gcloud auth activate-service-account ... --key-file: Must be specified. If the credentials were on the VM, then Docker could just mount those. Ordinarily credentials would be in .config/gcloud/ , and do this

All of a sudden having issues with deploying to GCP using gcloud app deploy . Created a brand new project and tried to upload a sample hello-world app from GCP, but still get the following error: ERROR: (gcloud.app.deploy) Error Response: [3] Docker image us.gcr.io/gcp-test-8710371/appengine/default.20181106t173450:latest was either not found, or is not in Docker V2 format. Please visit https://cloud.google.com/container-registry/docs/ui app.yaml: runtime: nodejs env: flex manual_scaling: instances: 1 resources: cpu: 1 memory_gb: 0.5 disk_size_gb: 10 SDK: Google Cloud SDK 224.0.0 I've checked