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

Can't pull images from local registry #555

Open
ghost opened this issue Dec 3, 2024 · 5 comments · May be fixed by #572
Open

Can't pull images from local registry #555

ghost opened this issue Dec 3, 2024 · 5 comments · May be fixed by #572

Comments

@ghost
Copy link

ghost commented Dec 3, 2024

We're missing configuration from the /etc/containerd/config.toml to allow kind to pull images from the local registry spun up by --registry.

I'll open a PR to add the configuration as part of the containerdConfigPatches in kind.go.

The required configuration is:

    [plugins."io.containerd.grpc.v1.cri".registry.mirrors]
      [plugins."io.containerd.grpc.v1.cri".registry.mirrors."kind-registry:5000"]
        endpoint = ["http://kind-registry:5000"]
    [plugins."io.containerd.grpc.v1.cri".registry.configs]
      [plugins."io.containerd.grpc.v1.cri".registry.configs."kind-registry:5000".tls]
        insecure_skip_verify = true

This configuration is required, e.g., for Apache Camel-K to be used with kn quickstart. Without this configuration, no images can be pulled from the local registry.

@psschwei
Copy link
Contributor

psschwei commented Dec 3, 2024

Thanks for opening the issue. Do you know if this is something impacting all local registry use, or is it something specific when using Camel-K?

@ghost
Copy link
Author

ghost commented Dec 3, 2024

As I understand it, this should impact all local registry use*. The issue is the kind can't pull from the local registry without either A) certificate configuration, or B) telling it that the local registry uses HTTP and that we should skip TLS verification.

*where the user is using the registry set up via the --registry flag.

Copy link

github-actions bot commented Mar 4, 2025

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 4, 2025
Evynglais pushed a commit to Evynglais/kn-plugin-quickstart that referenced this issue Mar 4, 2025
Evynglais added a commit to Evynglais/kn-plugin-quickstart that referenced this issue Mar 4, 2025
@Evynglais
Copy link

Evynglais commented Mar 4, 2025

Apologies for the delay and the confusion (closing and reopening the PR). I had a secondary account and have reopened the PR under my primary account and deleted the secondary.

The CLA requirement is now complete (which is what I believe you were waiting for me to do).

@Evynglais
Copy link

/reopen

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants