traefik-kop icon indicating copy to clipboard operation
traefik-kop copied to clipboard

Container fails to restart automatically after server reboot

Open Kuppit opened this issue 7 months ago • 6 comments

Hello,

I am experiencing an issue where the Traefik-Kop container does not restart automatically after a server reboot, despite having the restart: always policy set in the docker-compose.yml. After rebooting the server, the container exits with status code 2. The container logs do not provide further information on why the restart is not occurring.

Expected Behavior: The Traefik-Kop container should restart automatically after the server reboots.

Actual Behavior: The Traefik-Kop container does not restart and exits with status code 2.

Additional Information:

  • I have tried using tini as an init system in the Dockerfile, but the issue persists.
  • Using an entrypoint.sh script with signal handling and a restart loop did not resolve the issue.
  • The container runs a Go binary (traefik-kop) which interacts with Redis and Docker.

Any assistance or guidance on resolving this issue would be greatly appreciated. Thank you!

Kuppit avatar Jul 05 '24 08:07 Kuppit