Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot use private registry when unable to pull from docker.io #19353

Open
GavBurke opened this issue Jul 31, 2024 · 2 comments
Open

Cannot use private registry when unable to pull from docker.io #19353

GavBurke opened this issue Jul 31, 2024 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@GavBurke
Copy link

What Happened?

Trying to setup minikube's credential helpers for using a private docker repo, for the very reason because the network I am on can't pull from docker.io, but the credentials helper "plugin" is basically a pod that has to pull from docker.io to setup the credentials, making this plugin next-to-useless when trying to get around docker.io access

Attach the log file

Normal Scheduled 4m13s default-scheduler Successfully assigned kube-system/registry-creds-6cf4f8d55-4l7cq to minikube
Normal Pulling 2m39s (x4 over 4m13s) kubelet Pulling image "docker.io/upmcenterprises/registry-creds:1.10@sha256:93a633d4f2b76a1c66bf19c664dbddc56093a543de6d54320f19f585ccd7d605"
Warning Failed 2m38s (x4 over 4m12s) kubelet Failed to pull image "docker.io/upmcenterprises/registry-creds:1.10@sha256:93a633d4f2b76a1c66bf19c664dbddc56093a543de6d54320f19f585ccd7d605": Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden
Warning Failed 2m38s (x4 over 4m12s) kubelet Error: ErrImagePull
Warning Failed 2m26s (x6 over 4m12s) kubelet Error: ImagePullBackOff
Normal BackOff 2m14s (x7 over 4m12s) kubelet Back-off pulling image "docker.io/upmcenterprises/registry-creds:1.10@sha256:93a633d4f2b76a1c66bf19c664dbddc56093a543de6d54320f19f585ccd7d605"

Operating System

Ubuntu

Driver

Docker

@SamJSui
Copy link

SamJSui commented Aug 12, 2024

+1, also have this issue

@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants