Resolve the local cluster container registry without needing a port?

[neezer]

From the guide for local setup, I see I have to get the port for my registry using docker ps -f name=k3d-mycluster-registry and then tag my images on the host machine to include that address and port. Also, all my local k8s config files have to specify the port in order to pull the images correctly.

This works, but it's inconvenient. Is there any way to enable this workflow without using ports in the docker image tag?

---

I think I might have a workaround for this... still experimenting.

However,

the port, which the registry is listening on will be mapped to a random port on your host system

(from https://k3d.io/usage/guides/registries/#create-a-dedicated-registry-together-with-your-cluster)

Is there any way to make the host port mapping static instead of random?

[iwilltry42]

Hi @neezer , thanks for starting this discussion!

Is there any way to enable this workflow without using ports in the docker image tag?

Unfortunately not, as in the end, it's plain old networking and as long as it's not a standard port (like 80 for http or 443 for https), you'll have to specify a port (or setup some fancy proxy setup) 🤔

I have to get the port for my registry using docker ps -f name=k3d-mycluster-registry

This part I'd like to make a bit more convenient, by including the port in the log output at least.

Is there any way to make the host port mapping static instead of random?

Yep, create the registry standalone (i.e. not with --registry-create which is intentionally simplistic, but that may change in a later version): https://k3d.io/usage/guides/registries/#create-a-customized-k3d-managed-registry

[neezer]

Thanks! I eventually found that section in the link you provided and figured out how to create my customized k3d-managed registry with a static port, which has helped lots. I've also gone ahead with "some fancy proxy stuff" now that the port is static and I think I've got that working the way I wanted it to.