Help with Self Hosted Registry
Hi there,
I'm trying out Dokploy and already loving it! I'm managing a cluster with 3 local nodes (1 master, 2 workers). Everything is working as expected, but I need more details about the self-hosted registry setup. When this feature is enabled, I notice that a new container is created (confirmed using the docker ps command), and the correct port (5000) is exposed. However, no Traefik entrypoint is added to allow external access. Am I supposed to set this up manually? Why is there a Registry URL field if no Traefik proxy is linked to this container? Would also be very nice to have a local network only access to the registry, I mean just for the cluster nodes to access it with something like 192.168.1.xxx:5000 in the registry url field.
I know this might be a beginner's question, but given the "We set this up for you" statement in the self-hosted registry documentation, I was hoping for more information on the setup process.
Also made a discussion on GitHub
https://github.com/Dokploy/dokploy/discussions/525
GitHub
Self Hosted Registry Help Needed · Dokploy dokploy · Discussion #525
Hi there, I'm trying out Dokploy and already loving it! I need to manage a cluster with 3 local nodes (1 master, 2 workers). Everything is working as expected, but I need more details about the...
2 Replies
yeah by default is required to provide a domain name when using registry self hosted
I haven't considered the way to use internal networks
yes but actually no traefik route is created (also checked in traefik dashboard to be sure), i'm missing where the 5000 port Is forworded to 443 to be resolved to the DNS
could be so useful for local cluster