Alpine-Traefik restarts on its own #1045

Closed
opened 2026-02-04 22:45:19 +03:00 by OVERLORD · 6 comments
Owner

Originally created by @Redplcs on GitHub (May 31, 2025).

Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Traefik

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-traefik.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Alpine

📝 Provide a clear and concise description of the issue.

After you're starting LXC container with Alpine OS, Traefik after small amount of time restarts. You can check this behavior by running rc-status. Traefik restarts and after around 5 or 7 restarts shows failed status. I've checked the logs and It seems like Traefik after initialization stops throwing messages I have to go... and Stopping server gracefully. Looks like something sends SIGINT into Traefik. I've took launch command from OpenRC and run Traefik with traefik --configFile=/etc/traefik/traefik.yaml and after 5 minutes everything fine. I see only a single I have to go... message. I think the problem is in OpenRC service file. After Traefik launch it's closes it automatically. Can it skip close step or whatever it called

🔄 Steps to reproduce the issue.

  • Just install script and run container

Paste the full error output (if available).

traefik-running-through-openrc.log
traefik-running-manually.log

🖼️ Additional context (optional).

No response

Originally created by @Redplcs on GitHub (May 31, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Traefik ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-traefik.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Alpine ### 📝 Provide a clear and concise description of the issue. After you're starting LXC container with Alpine OS, Traefik after small amount of time restarts. You can check this behavior by running `rc-status`. Traefik restarts and after around 5 or 7 restarts shows `failed` status. I've checked the logs and It seems like Traefik after initialization stops throwing messages `I have to go...` and `Stopping server gracefully`. Looks like something sends SIGINT into Traefik. I've took launch command from OpenRC and run Traefik with `traefik --configFile=/etc/traefik/traefik.yaml` and after 5 minutes everything fine. I see only a single `I have to go...` message. I think the problem is in `OpenRC` service file. After Traefik launch it's closes it automatically. Can it skip `close` step or whatever it called ### 🔄 Steps to reproduce the issue. - Just install script and run container ### ❌ Paste the full error output (if available). [traefik-running-through-openrc.log](https://github.com/user-attachments/files/20533832/traefik-with-openrc.log) [traefik-running-manually.log](https://github.com/user-attachments/files/20533833/traefik-manually-running.log) ### 🖼️ Additional context (optional). _No response_
OVERLORD added the external label 2026-02-04 22:45:19 +03:00
Author
Owner

@tremor021 commented on GitHub (May 31, 2025):

I don't have those issues on any of my nodes

@tremor021 commented on GitHub (May 31, 2025): I don't have those issues on any of my nodes
Author
Owner

@MickLesk commented on GitHub (May 31, 2025):

SIGINT. Sure thats not from Proxmox node? Have this in past by broken RAM

@MickLesk commented on GitHub (May 31, 2025): SIGINT. Sure thats not from Proxmox node? Have this in past by broken RAM
Author
Owner

@Redplcs commented on GitHub (May 31, 2025):

@tremor021 I found out why this happens. Try to install LXC container with Alpine-Traefik and delete ping: {} in static configuration. This prevent Traefik to restart by OpenRC. I assume that init script tries to healthcheck the service (It even has healthcheck_timer=30 and this is the interval when Traefik restarts). And when you're starting Traefik with traefik --configFile=/etc/traefik/traefik.yaml everything fine

@Redplcs commented on GitHub (May 31, 2025): @tremor021 I found out why this happens. Try to install LXC container with Alpine-Traefik and delete `ping: {}` in static configuration. This prevent Traefik to restart by OpenRC. I assume that init script tries to healthcheck the service (It even has `healthcheck_timer=30` and this is the interval when Traefik restarts). And when you're starting Traefik with `traefik --configFile=/etc/traefik/traefik.yaml` everything fine
Author
Owner

@tremor021 commented on GitHub (May 31, 2025):

Then its a bug in Traefik itself, since it a autogenerated config file, we are not touching it at all, except enabling Dashboard to be accessible on 0.0.0.0 in traefik.yaml

I can remove the lines for healthcheck, no problem

@tremor021 commented on GitHub (May 31, 2025): Then its a bug in Traefik itself, since it a autogenerated config file, we are not touching it at all, except enabling Dashboard to be accessible on 0.0.0.0 in `traefik.yaml` I can remove the lines for healthcheck, no problem
Author
Owner

@Redplcs commented on GitHub (May 31, 2025):

I think it's an issue of Alpine community. I see that the script uses apk add traefik from community repository. I will create new issue on alpine's gitlab then.

Here's the traefik repo on alpine: https://gitlab.alpinelinux.org/alpine/aports/-/tree/master/community/traefik

@Redplcs commented on GitHub (May 31, 2025): I think it's an issue of Alpine community. I see that the script uses `apk add traefik` from community repository. I will create new issue on alpine's gitlab then. Here's the traefik repo on alpine: https://gitlab.alpinelinux.org/alpine/aports/-/tree/master/community/traefik
Author
Owner

@tremor021 commented on GitHub (Jun 1, 2025):

Then its better to solve it at the package level than for me to do dirty fix on a config file

@tremor021 commented on GitHub (Jun 1, 2025): Then its better to solve it at the package level than for me to do dirty fix on a config file
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1045