registrator VS traefik-kop

Had the same problem recently, and was close to building a tool like yours. But I discovered Registrator. I added a small Consul instance and the consul provider configuration to traefik. Registrator ( https://github.com/gliderlabs/registrator ) automatically registers new docker services on the second maschine. Stopped services are automatically unregistered. Had to cross build Registrator for arm64, but this was simple using Docker BuildX.

Traefik gives you a lot of options to accomplish this, you can use docker swarm, move to kubernetes or use any of their discovery providers. These options were rather complicated solutions for what I needed, so I decided to look around for other alternatives. Here I found Traefik-Kop, but it I still had to do a lot of manual work and open a different port for each container I wanted to be accesible through my reverse proxy.

The obvious solution is docker swarm/kubernetes, but if you don't want to go all the way there yet I can really recommend traefik kop. Very simple to setup, you just add a redis service next to the traefik instance and set it up as a provider, then you run traefik kop on every other machine, pointed at that redis service. Traefik kop will discover docker services on the machine and write everything to redis and it'll get picked up ny traefik. Worked like a charm!

Maybe this can help you https://github.com/jittering/traefik-kop