Hey folks, I'm having some issues with my Docker setup on a Debian server. I've got a complex composition of four containers: unbound, pihole, traefik, and netbird, organized to start in a specific order using the `depends_on` feature. Everything's working fine until I reboot the server. After the reboot, all containers start successfully except Traefik, which exits with an error. If I wait a bit and redeploy the setup, or even manually start the Traefik container afterwards, it works fine.
Here's the order of dependencies: pihole depends on unbound, traefik depends on pihole, and netbird depends on traefik. I really want this to work on startup without needing to go through redeployment or manual restarts, since Traefik is critical for my network management.
I've attached the relevant error from the Traefik logs for more context. Any ideas on why Traefik fails to start initially, and how I can fix this within my existing Docker Compose setup? Happy to share my Docker Compose file if needed!
2 Answers
It looks like your Traefik service might be missing a restart policy, which is why it's not starting automatically after the reboot. By default, Docker won't restart containers unless specified. Try setting `restart: always` for the Traefik service to ensure it starts up when the system reboots. You can check out the Docker documentation for more details on automatic container startups.
You might want to investigate if the issue is related to the timing of your system's startup. It’s possible that Traefik is trying to bind to its ports before the network stack is fully up. A possible fix could be to add a delay to Traefik's startup process or implement a custom health check that ensures the network is ready before Traefik runs. There’s a discussion on Docker's startup order that could be helpful, check it out!
I did try changing the restart policy to `always`, but unfortunately, it didn't solve the issue. I'm still seeing the same problem.