docker pull gcr.io/k8s-staging-multitenancy/hnc-manager:v0.8.0

Question

docker pull gcr.io/k8s-staging-multitenancy/hnc-manager:v0.8.0

admin-zoujing opened this issue 3 years ago · comments

Can you put the image into the local folder to download? This address is very difficult to download.

Adrian Ludwin · Answer 1 · Tue Jul 13 2021 21:48:20 GMT+0800 (China Standard Time)

I'm not sure what you mean by a "local folder?" Docker images are almost exclusively distributed from a Docker registry like the Docker Hub or gcr.io .

…

On Tue, 13 Jul 2021, 5:08 am Zou Jing, ***@***.***> wrote: Can you put the image into the local folder to download? This address is very difficult to download. docker pull gcr.io/k8s-staging-multitenancy/hnc-manager:v0.8.0 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1514>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE43PZHMFGPZMBO7WWN3NF3TXP67HANCNFSM5AITULUQ> .

Kubernetes Triage Robot · Answer 2 · Mon Oct 11 2021 22:22:33 GMT+0800 (China Standard Time)

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Kubernetes Triage Robot · Answer 3 · Wed Nov 10 2021 22:58:57 GMT+0800 (China Standard Time)

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

Kubernetes Triage Robot · Answer 4 · Fri Dec 10 2021 23:18:01 GMT+0800 (China Standard Time)

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue or PR with /reopen
Mark this issue or PR as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Kubernetes Prow Robot · Answer 5 · Fri Dec 10 2021 23:19:16 GMT+0800 (China Standard Time)

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue or PR with /reopen

Mark this issue or PR as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.