Skip to content
This repository has been archived by the owner on Feb 8, 2021. It is now read-only.

can't use google cloud registry with hyper.sh #261

Open
hixus opened this issue Jun 25, 2018 · 1 comment
Open

can't use google cloud registry with hyper.sh #261

hixus opened this issue Jun 25, 2018 · 1 comment
Assignees

Comments

@hixus
Copy link

hixus commented Jun 25, 2018

Tried to use gcr registry but it seems to complain "Pulling repository eu.gcr.io/xxx/xxx
Error: Status 405 trying to pull repository xxx/xxx: "v1 Registry API is disabled. If you are not explicitly using the v1 Registry API, it is possible your v2 image could not be found. Verify that your image is available, or retry with dockerd --disable-legacy-registry. See https://cloud.google.com/container-registry/docs/support/deprecation-notices""

My client seems to be latest version:
Client:
Version: 1.10.16
API version: 1.23
Go version: go1.8.3
Git commit: 860cca2
Built: Sat, Sep 30, 2017 12:59:00 PM
OS/Arch: windows/amd64

@Jimmy-Xu
Copy link
Contributor

@hixus

If you want to pull a private image from GCR, you need to run hyper login first.

authentication with google access token

$ hyper login -u oauth2accesstoken -p "$(gcloud auth print-access-token)" https://gcr.io

or

authentication with google json file

$ hyper login -u _json_key -p "$(cat keyfile.json)" https://gcr.io

If you want to pull a public image from GCR, Here is an example:

$ hyper pull gcr.io/google-containers/busybox
Using default tag: latest
latest: Pulling from google-containers/busybox
a3ed95caeb02: Pull complete
138cfc514ce4: Pull complete
Digest: sha256:d8d3bc2c183ed2f9f10e7258f84971202325ee6011ba137112e01e30f206de67
Status: Downloaded newer image for gcr.io/google-containers/busybox:latest

@Jimmy-Xu Jimmy-Xu self-assigned this Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants