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 · 5 comments

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

Answer 1 · 2021-07-13T13:48:20.000Z

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> .

Answer 2 · 2021-10-11T14:22:33.000Z

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

Answer 3 · 2021-11-10T14:58:57.000Z

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

Answer 4 · 2021-12-10T15:18:01.000Z

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

Answer 5 · 2021-12-10T15:19:16.000Z

@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.