[HELP] Pushing to the local registry

[devalexandre]

create register k3d registry create registry --port=5000

then create the cluster using register k3d cluster create --registry-use k3d-registry:5000

use alpine image for testing

docker pull alpine:latest

change image tag docker tag alpine:latest k3d-registry:5000/testimage:local
pull the image to the register

docker push k3d-registry:5000/testimage:local
error Get "https://k3d-registry:5000/v2/": dial tcp: lookup k3d-registry: no such host

reference:
https://k3d.io/usage/guides/registries

Which OS & Architecture

• Linux, amd64

Which version of k3d

k3d version v5.0.0
k3s version v1.21.5-k3s1 (default)

Which version of docker

• output of docker version

Client:
 Version:           20.10.9
 API version:       1.41
 Go version:        go1.17.1
 Git commit:        c2ea9bc90b
 Built:             Mon Oct  4 19:13:02 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.9
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.17.1
  Git commit:       79ea9d3080
  Built:            Mon Oct  4 19:12:03 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.5.7
  GitCommit:        8686ededfc90076914c5238eb96c883ea093a8ba.m
 runc:
  Version:          1.0.2
  GitCommit:        v1.0.2-0-g52b36a2d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

 docker info  
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Build with BuildKit (Docker Inc., v0.6.1-docker)
  compose: Docker Compose (Docker Inc., 2.0.1)

Server:
 Containers: 3
  Running: 3
  Paused: 0
  Stopped: 0
 Images: 22
 Server Version: 20.10.9
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: false
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8686ededfc90076914c5238eb96c883ea093a8ba.m
 runc version: v1.0.2-0-g52b36a2d
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.14.11-arch1-1
 Operating System: Linux
 OSType: linux
 Architecture: x86_64
 CPUs: 12
 Total Memory: 15.56GiB
 Name: melissa
 ID: NSC3:RLS5:73LI:BCRF:QVF7:7TCR:OUZ4:W24S:FI74:OTXZ:TLN7:NK7T
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Username: alephp
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

[iwilltry42]

Hi @devalexandre , thanks for opening this issue!
Sorry for the long wait time, I just got around to cleaning up the backlog now.

Did you see that section about resolving the registry from your local machine? See https://k3d.io/stable/usage/registries/#pushing-to-your-local-registry-address

The point is, that k3d-registry is the name of the docker container, which is not known to your host.
You can instead push to localhost:5000 (because the port is exposed on your host) or somehow make your system resolve k3d-registry to 127.0.0.1 (localhost).
Within the docker network (or k3d cluster) you can use the name k3d-registry because it's going to be resolved by Docker's built-in DNS (or CoreDNS inside the cluster).

[adamluzsi]

For reference, here's the active link as it currently stands:
https://k3d.io/v5.5.2/usage/registries/#pushing-to-your-local-registry-address

[iwilltry42]

Thanks @adamluzsi , I updated the original comment to use the /stable/ redirect to the latest stable tag 👍