[HELP] Using the new k3d-managed local registry

[gurkang]

What did you do

• How was the cluster created?

  • k3d cluster create test --registry-create

• What did you do afterwards?

PS C:\Users\USER> docker ps -f name=k3d-test-registry
CONTAINER ID   IMAGE        COMMAND                  CREATED          STATUS         PORTS                     NAMES
6e39652fd61c   registry:2   "/entrypoint.sh /etc…"   35 minutes ago   Up 8 minutes   0.0.0.0:57061->5000/tcp   k3d-test-registry

PS C:\Users\USER> k3d registry list
NAME                ROLE       CLUSTER   STATUS
k3d-test-registry   registry   test      running

1. k3d tag client:test k3d-test-registry:5000/client:test
2. k3d push k3d-test-registry:5000/client:test

What did you expect to happen

I expected to see a successful message after pushing and being able to use my new image.

Screenshots or terminal output

PS C:\Users\USER> docker push k3d-test-registry:5000/client:test
The push refers to repository [k3d-test-registry:5000/client]
Get https://k3d-test-registry:5000/v2/: dial tcp: lookup k3d-test-registry on 192.168.65.5:53: no such host

Which OS & Architecture

Windows 10

Which version of k3d

k3d version v4.4.4
k3s version v1.20.6-k3s1 (default)

Which version of docker

Client:
 Cloud integration: 1.0.14
 Version:           20.10.6
 API version:       1.41
 Go version:        go1.16.3
 Git commit:        370c289
 Built:             Fri Apr  9 22:49:36 2021
 OS/Arch:           windows/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.6
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       8728dd2
  Built:            Fri Apr  9 22:44:56 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.4
  GitCommit:        05f951a3781f4f2c1911b05e61c160e9c30eaa8e
 runc:
  Version:          1.0.0-rc93
  GitCommit:        12644e614e25b05da6fd08a38ffa0cfe1903fdec
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

[iwilltry42]

Hi @gurkang , thanks for opening this issue!
So your registry is running in a docker container called k3d-test-registry.
Other containers can resolve this name thanks to docker DNS.
Your local machine however does not now about it (and neither your DNS Server, if you have one).
So you have to tell it about this new entity.

Easiest way would be to put k3d-test-registry 127.0.0.1 into your hosts file (/etc/hosts on Mac and Linux). (FWIW: just for pushing you can also use localhost:5000 directly)