Static configuration limits hot-reload for entrypoint ports in Traefik dev environment

Resolution

Entrypoint values cannot be defined via dynamic configuration. In Traefik, entrypoints are strictly part of the static configuration layer; they define the physical network sockets the process opens. Because these sockets are bound at startup, they cannot be modified, added, or removed without restarting the Traefik process.

The Technical Constraint

Traefik separates configuration into two distinct layers: static and dynamic. Entrypoints (the ports and addresses Traefik listens on) belong to the static layer. Dynamic configuration—handled via Docker labels, Kubernetes Ingress, or the File provider—is used to define how traffic is routed after it has entered an existing entrypoint. Attempting to define an entrypoint via a container label or a dynamic YAML file will result in the configuration being ignored or triggering a log warning.

Trade-offs and Alternatives

Since you cannot hot-reload the port itself, you must choose between the following strategies based on your development needs:

• Static Over-Provisioning: Define all potential entrypoints you might need (e.g., 80, 443, 8080, 8443) in your static config at the start. You can then dynamically route traffic to different services using these ports without restarting.
• Container Orchestration: If you are using Docker Compose, use docker compose restart traefik. While this is a restart, it is generally faster than a full teardown and rebuild.
• Middleware vs. Entrypoints: Middleware can modify requests (headers, redirects, authentication) and is fully dynamic. However, middleware cannot change the port the server is listening on; it can only act on traffic already accepted by a static entrypoint.

Verification Steps

To confirm that a change to your static configuration (like traefik.yml) has not been applied, you can run the following command to check which ports are currently bound by the process:

netstat -tulpn | grep traefik

If you edit the static file and the output of the command above does not change, the configuration has not been reloaded, confirming the requirement for a process restart.

Diagnostic Detail Needed

Are you using a specific orchestration tool (e.g., Docker Compose, Kubernetes, or standalone binary) to manage the Traefik process? The recommendation for automating the restart loop differs depending on the environment.