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

Idlewatcher fails to reconnect to awoken container #119

New Issue
Closed
opened 2025-12-29 09:23:22 +01:00 by adam · 3 comments
adam commented 2025-12-29 09:23:22 +01:00
Owner
Copy Link

Originally created by @scottsweb on GitHub (Nov 6, 2025).

I am testing GoDoxy with Podman and the idle-sleep/watcher service. My compose.yml file has these sections:

    labels:
      io.containers.autoupdate: registry
      proxy.aliases: glance
      proxy.idle_timeout: 30s
    networks:
      - proxy

In the logs I can see the container being stopped:

11-06 21:01 INF container stopped container=glance deps=[] idle_timeout=30s kind=docker
11-06 21:01 INF idle timeout container=glance deps=[] idle_timeout=30s kind=docker

And the result of that looks good:

CONTAINER ID  IMAGE                                  COMMAND     CREATED             STATUS                     PORTS                                                           NAMES
9268cc275d93  ghcr.io/yusing/socket-proxy:latest     /app/run    33 minutes ago      Up 33 minutes              127.0.0.1:2375->2375/tcp                                        godoxy-socket-proxy
dd2d5d1e4408  docker.io/glanceapp/glance:latest                  About a minute ago  Exited (2) 14 seconds ago  8080/tcp                                                        glance
ad55efb5bc16  ghcr.io/yusing/godoxy:latest           /app/run    About a minute ago  Up About a minute          0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:443->443/udp  godoxy
41bce01249b4  ghcr.io/yusing/godoxy-frontend:latest  server.js   About a minute ago  Up About a minute          3000/tcp                                                        godoxy-frontend

Visiting the URL starts the container again:

11-06 21:01 INF awaken container=glance deps=[] idle_timeout=30s kind=docker

CONTAINER ID  IMAGE                                  COMMAND     CREATED             STATUS             PORTS                                                           NAMES
9268cc275d93  ghcr.io/yusing/socket-proxy:latest     /app/run    33 minutes ago      Up 33 minutes      127.0.0.1:2375->2375/tcp                                        godoxy-socket-proxy
dd2d5d1e4408  docker.io/glanceapp/glance:latest                  About a minute ago  Up 5 seconds       8080/tcp                                                        glance
ad55efb5bc16  ghcr.io/yusing/godoxy:latest           /app/run    About a minute ago  Up About a minute  0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:443->443/udp  godoxy
41bce01249b4  ghcr.io/yusing/godoxy-frontend:latest  server.js   About a minute ago  Up About a minute  3000/tcp                                                        godoxy-frontend

The container monitor sees it as started:

Image

But in the browser I remain stuck on this screen:

Image

There is an error in console:

Uncaught (in promise) TypeError: NetworkError when attempting to fetch resource.

I'll see what else I can discover.

Originally created by @scottsweb on GitHub (Nov 6, 2025). I am testing GoDoxy with Podman and the idle-sleep/watcher service. My `compose.yml` file has these sections: ``` labels: io.containers.autoupdate: registry proxy.aliases: glance proxy.idle_timeout: 30s networks: - proxy ``` In the logs I can see the container being stopped: ``` 11-06 21:01 INF container stopped container=glance deps=[] idle_timeout=30s kind=docker 11-06 21:01 INF idle timeout container=glance deps=[] idle_timeout=30s kind=docker ``` And the result of that looks good: ``` CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9268cc275d93 ghcr.io/yusing/socket-proxy:latest /app/run 33 minutes ago Up 33 minutes 127.0.0.1:2375->2375/tcp godoxy-socket-proxy dd2d5d1e4408 docker.io/glanceapp/glance:latest About a minute ago Exited (2) 14 seconds ago 8080/tcp glance ad55efb5bc16 ghcr.io/yusing/godoxy:latest /app/run About a minute ago Up About a minute 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:443->443/udp godoxy 41bce01249b4 ghcr.io/yusing/godoxy-frontend:latest server.js About a minute ago Up About a minute 3000/tcp godoxy-frontend ``` Visiting the URL starts the container again: ``` 11-06 21:01 INF awaken container=glance deps=[] idle_timeout=30s kind=docker ``` ``` CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9268cc275d93 ghcr.io/yusing/socket-proxy:latest /app/run 33 minutes ago Up 33 minutes 127.0.0.1:2375->2375/tcp godoxy-socket-proxy dd2d5d1e4408 docker.io/glanceapp/glance:latest About a minute ago Up 5 seconds 8080/tcp glance ad55efb5bc16 ghcr.io/yusing/godoxy:latest /app/run About a minute ago Up About a minute 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:443->443/udp godoxy 41bce01249b4 ghcr.io/yusing/godoxy-frontend:latest server.js About a minute ago Up About a minute 3000/tcp godoxy-frontend ``` The container monitor sees it as started: <img width="718" height="90" alt="Image" src="https://github.com/user-attachments/assets/8e247820-53d8-42e5-90c4-2e84d9260c31" /> But in the browser I remain stuck on this screen: <img width="774" height="720" alt="Image" src="https://github.com/user-attachments/assets/31acc321-c0d4-4271-b7ef-514acd39ba6e" /> There is an error in console: ``` Uncaught (in promise) TypeError: NetworkError when attempting to fetch resource. ``` I'll see what else I can discover.
adam closed this issue 2025-12-29 09:23:22 +01:00
adam commented 2025-12-29 09:23:22 +01:00
Author
Owner
Copy Link

@scottsweb commented on GitHub (Nov 6, 2025):

Using proxy.stop_method: pause seems to work, I do not get stuck at the glance is starting... screen and am re-directed as expected most of the time, although I have seen some Internal server error notices.

The internal server seems to be caught in the logs:

11-06 22:14 INF unpausing container container=glance deps=[] idle_timeout=30s kind=docker
11-06 22:14 INF unpausing container container=glance deps=[] idle_timeout=30s kind=docker
11-06 22:14 ERR failed to wake: watcher "glance" error: Error response from daemon: "826fed96db8ccb59af66ec0f29eb702bae1d8c5edcdbcd4a74dfb7f08abed7fc" is not paused, can't unpause: container state improper host=glance.domain.com remote=10.89.1.3:40746 uri="GET /"
@scottsweb commented on GitHub (Nov 6, 2025): Using `proxy.stop_method: pause` seems to work, I do not get stuck at the `glance is starting...` screen and am re-directed as expected most of the time, although I have seen some `Internal server error` notices. The internal server seems to be caught in the logs: ``` 11-06 22:14 INF unpausing container container=glance deps=[] idle_timeout=30s kind=docker 11-06 22:14 INF unpausing container container=glance deps=[] idle_timeout=30s kind=docker 11-06 22:14 ERR failed to wake: watcher "glance" error: Error response from daemon: "826fed96db8ccb59af66ec0f29eb702bae1d8c5edcdbcd4a74dfb7f08abed7fc" is not paused, can't unpause: container state improper host=glance.domain.com remote=10.89.1.3:40746 uri="GET /" ```
adam commented 2025-12-29 09:23:22 +01:00
Author
Owner
Copy Link

@yusing commented on GitHub (Nov 7, 2025):

Try v0.20.7, please report back whether it works for you

@yusing commented on GitHub (Nov 7, 2025): Try v0.20.7, please report back whether it works for you
adam commented 2025-12-29 09:23:22 +01:00
Author
Owner
Copy Link

@scottsweb commented on GitHub (Nov 7, 2025):

Looks to be working perfectly with both stop and pause. Thank you!

@scottsweb commented on GitHub (Nov 7, 2025): Looks to be working perfectly with both `stop` and `pause`. Thank you!
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#119
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?