Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
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.
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.
Related posts
- Can an already running Traefik container on a network act as revesre proxy for co tainers on another network
- Traefik vs NPM vs alternative for multiple machines
- Routing traffic from another machine
- Running traefik with multiple docker hosts
- New tool: traefik-kop - a discovery agent for non-swarm/k8s docker clusters