starred/godoxy-yusing
1
0
Fork 0
mirror of https://github.com/yusing/godoxy.git synced 2026-01-14 07:33:36 +01:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

Idle timeout for a running docker service stuck with "starting" status #101

New Issue
Closed
opened 2025-12-29 14:24:56 +01:00 by adam · 5 comments
adam commented 2025-12-29 14:24:56 +01:00
Owner
Copy Link

Originally created by @mrg358 on GitHub (Aug 27, 2025).

Tested with 2 services Stirling-PDF and Lingva.

Stirling-PDF container running and working but reports no "healthy" status, just "running". This container is a bit heavy and boots up cca 30-60s. In Godoxy it is stuck forever with a blue "starting" status. Stirling page doesnt open, only the "starting page" shows up.

Docker Compose Stirling

    labels:
      proxy.aliases: stirling-pdf
      proxy.idle_timeout: 15m

Lingva container is running with a "healthy" status. After booting up it switches from "blue starting" status to a "green healthy" status in Godoxy. After timeout it fails to shutdown. It switches back to a "blue starting" status. Lingva page opens despite having a "blue starting" status.

Docker Compose Lingva

    labels:
      proxy.aliases: lingva
      proxy.idle_timeout: 15m

Docker Logs

f4c578742937   docker.stirlingpdf.com/stirlingtools/stirling-pdf:latest   "tini -- /scripts/in…"   19 minutes ago   Up 4 minutes              8080/tcp                                                                               stirling-pdf-stirling-pdf-1
f3980497d6c7   thedaviddelta/lingva-translate:latest                      "docker-entrypoint.s…"   5 minutes ago    Up 5 minutes (healthy)    3000/tcp                                                                               lingva

Godoxy Logs

godoxy-proxy     | 08-27 21:14 INF idlewatcher stopped container=lingva deps=[] idle_timeout=10m0s kind=docker
godoxy-proxy     | 08-27 21:14 INF http_routes: removed lingva
godoxy-proxy     | 08-27 21:14 INF idlewatcher started container=lingva deps=[] idle_timeout=15m0s kind=docker
godoxy-proxy     | 08-27 21:14 INF http_routes: added lingva
godoxy-proxy     | 08-27 21:14 INF http_routes: removed lingva
godoxy-proxy     | 08-27 21:14 INF http_routes: added lingva
godoxy-proxy     | 08-27 21:15 INF idlewatcher stopped container=stirling-pdf-stirling-pdf-1 deps=[] idle_timeout=1h0m30s kind=docker
godoxy-proxy     | 08-27 21:15 INF http_routes: removed stirling-pdf
godoxy-proxy     | 08-27 21:15 INF idlewatcher started container=stirling-pdf-stirling-pdf-1 deps=[] idle_timeout=15m0s kind=docker
godoxy-proxy     | 08-27 21:15 INF http_routes: added stirling-pdf
godoxy-proxy     | 08-27 21:15 INF http_routes: removed stirling-pdf
godoxy-proxy     | 08-27 21:15 INF http_routes: added stirling-pdf
Originally created by @mrg358 on GitHub (Aug 27, 2025). Tested with 2 services Stirling-PDF and Lingva. Stirling-PDF container running and working but reports no "healthy" status, just "running". This container is a bit heavy and boots up cca 30-60s. In Godoxy it is stuck forever with a blue "starting" status. Stirling page doesnt open, only the "starting page" shows up. Docker Compose Stirling ``` labels: proxy.aliases: stirling-pdf proxy.idle_timeout: 15m ``` Lingva container is running with a "healthy" status. After booting up it switches from "blue starting" status to a "green healthy" status in Godoxy. After timeout it fails to shutdown. It switches back to a "blue starting" status. Lingva page opens despite having a "blue starting" status. Docker Compose Lingva ``` labels: proxy.aliases: lingva proxy.idle_timeout: 15m ``` Docker Logs ``` f4c578742937 docker.stirlingpdf.com/stirlingtools/stirling-pdf:latest "tini -- /scripts/in…" 19 minutes ago Up 4 minutes 8080/tcp stirling-pdf-stirling-pdf-1 f3980497d6c7 thedaviddelta/lingva-translate:latest "docker-entrypoint.s…" 5 minutes ago Up 5 minutes (healthy) 3000/tcp lingva ``` Godoxy Logs ``` godoxy-proxy | 08-27 21:14 INF idlewatcher stopped container=lingva deps=[] idle_timeout=10m0s kind=docker godoxy-proxy | 08-27 21:14 INF http_routes: removed lingva godoxy-proxy | 08-27 21:14 INF idlewatcher started container=lingva deps=[] idle_timeout=15m0s kind=docker godoxy-proxy | 08-27 21:14 INF http_routes: added lingva godoxy-proxy | 08-27 21:14 INF http_routes: removed lingva godoxy-proxy | 08-27 21:14 INF http_routes: added lingva godoxy-proxy | 08-27 21:15 INF idlewatcher stopped container=stirling-pdf-stirling-pdf-1 deps=[] idle_timeout=1h0m30s kind=docker godoxy-proxy | 08-27 21:15 INF http_routes: removed stirling-pdf godoxy-proxy | 08-27 21:15 INF idlewatcher started container=stirling-pdf-stirling-pdf-1 deps=[] idle_timeout=15m0s kind=docker godoxy-proxy | 08-27 21:15 INF http_routes: added stirling-pdf godoxy-proxy | 08-27 21:15 INF http_routes: removed stirling-pdf godoxy-proxy | 08-27 21:15 INF http_routes: added stirling-pdf ```
adam closed this issue 2025-12-29 14:24:56 +01:00
adam commented 2025-12-29 14:24:57 +01:00
Author
Owner
Copy Link

@yusing commented on GitHub (Aug 28, 2025):

Hi, will investigate into this later and reply back.

@yusing commented on GitHub (Aug 28, 2025): Hi, will investigate into this later and reply back.
adam commented 2025-12-29 14:24:58 +01:00
Author
Owner
Copy Link

@yusing commented on GitHub (Sep 5, 2025):

I have noticed this issue and figured out the root cause. Will push a fix soon.

@yusing commented on GitHub (Sep 5, 2025): I have noticed this issue and figured out the root cause. Will push a fix soon.
adam commented 2025-12-29 14:24:59 +01:00
Author
Owner
Copy Link

@yusing commented on GitHub (Sep 8, 2025):

Hi @mrg358 do you still see the issue?

@yusing commented on GitHub (Sep 8, 2025): Hi @mrg358 do you still see the issue?
adam commented 2025-12-29 14:24:59 +01:00
Author
Owner
Copy Link

@mrg358 commented on GitHub (Sep 8, 2025):

I tested this today on the latest GoDoxy v0.17.4 with two small containers (cup, wallos) and two larger ones (lingva, stirling) with longer startup times.

All four of them are working reliably now. Three of them have no health check and show only a "running" status in Docker, while Lingva shows a "healthy" status. I tested this with a single label: proxy.idle_timeout: 15m. All containers went to sleep automatically, and I was able to successfully wake them up multiple times.

It looks like my issues are solved. 👍

Relevant side notice:
I struggled a bit while testing. My GoDoxy frontend was broken in the browser, which must have been some kind of cache issue. Changing the config in the CLI wasn't reflected in the Web UI. I started fresh in an incognito window, and everything was fine. This could have also been causing some of the problems related to this issue, so I've learned my lesson to clear cookies and site data next time. I don't like to do it too often, though, because it clears cookies for all services under my main domain.
Edit: opened a new bug report likely related to this issue.

The idle time feature is especially useful for large containers to free up memory on the Docker host. I will continue testing this feature and will report any issues I find.

@mrg358 commented on GitHub (Sep 8, 2025): I tested this today on the latest GoDoxy v0.17.4 with two small containers (cup, wallos) and two larger ones (lingva, stirling) with longer startup times. All four of them are working reliably now. Three of them have no health check and show only a "running" status in Docker, while Lingva shows a "healthy" status. I tested this with a single label: `proxy.idle_timeout: 15m`. All containers went to sleep automatically, and I was able to successfully wake them up multiple times. It looks like my issues are solved. 👍 Relevant side notice: I struggled a bit while testing. My GoDoxy frontend was broken in the browser, which must have been some kind of cache issue. Changing the config in the CLI wasn't reflected in the Web UI. I started fresh in an incognito window, and everything was fine. This could have also been causing some of the problems related to this issue, so I've learned my lesson to clear cookies and site data next time. I don't like to do it too often, though, because it clears cookies for all services under my main domain. Edit: opened a [new bug report](https://github.com/yusing/godoxy/issues/147#issue-3395300810) likely related to this issue. The idle time feature is especially useful for large containers to free up memory on the Docker host. I will continue testing this feature and will report any issues I find.
adam commented 2025-12-29 14:25:00 +01:00
Author
Owner
Copy Link

@yusing commented on GitHub (Sep 9, 2025):

Thanks a lot. Closing this now.

@yusing commented on GitHub (Sep 9, 2025): Thanks a lot. Closing this now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
pull-request
Mirrored from GitHub Pull Request
 wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/godoxy-yusing#101
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?