Local registry not working with tag -> digest resolution

[evankanderson]

I'm attempting to set up a cluster using kn quickstart kind --registry.

I'm able to build and push to the registry, but when I try to use an image that I've pushed to my local registry on localhost:5001, I get:

kn service create dashboard --image localhost:5001/dashboard --port 3000
Creating service 'dashboard' in namespace 'default':

  0.024s The Route is still working to reflect the latest desired specification.
  0.038s ...
  0.051s Configuration "dashboard" is waiting for a Revision to become ready.
  0.056s Revision "dashboard-00001" failed with message: Unable to fetch image "localhost:5001/dashboard": failed to resolve image to digest: Get "https://localhost:5001/v2/": dial tcp [::1]:5001: connect: connection refused; Get "http://localhost:5001/v2/": dial tcp [::1]:5001: connect: connection refused.
  0.060s Configuration "dashboard" does not have any ready Revision.
Error: RevisionFailed: Revision "dashboard-00001" failed with message: Unable to fetch image "localhost:5001/dashboard": failed to resolve image to digest: Get "https://localhost:5001/v2/": dial tcp [::1]:5001: connect: connection refused; Get "http://localhost:5001/v2/": dial tcp [::1]:5001: connect: connection refused.

It appears that we could set registries-skipping-tag-resolving in config-deployment to work around this, though I'm also seeing issues pulling the underlying images, and the Kind project has switched to a new set of configuration options: kubernetes-sigs/kind#2875

[evankanderson]

Actually, it looks like I'd torn down and re-started the kind cluster and cleared the local registry in the process. The following patch seems to enable kn service create, though it would be nice if there were a setting to enable remapping registry URLs to match the containerd one.

kubectl patch cm -n knative-serving config-deployment --patch '{"data":{"registries-skipping-tag-resolving":"localhost:5001"}}'