search

ItsEcholot / ContainerNursery

Puts Docker Containers to sleep and wakes them back up when they're needed
MIT License
95 stars 6 forks source link

Some containers not starting after last update #8

Closed fitur closed 3 years ago

fitur commented 3 years ago

Log: INFO [2021-09-11 07:09:20.155 +0200]: (Re)loading hosts, clearing all existing hosts first INFO [2021-09-11 07:09:20.155 +0200]: Added proxy host host: "code.domain.com" container: "code-server" proxy: { "host": "code-server.lsio", "port": 8443 } timeoutSeconds: 300 INFO [2021-09-11 07:09:20.161 +0200]: Added proxy host host: "home.domain.com" container: "homer" proxy: { "host": "homer.lsio", "port": 8080 } timeoutSeconds: 300 INFO [2021-09-11 07:09:20.162 +0200]: Added proxy host host: "test.domain.com" container: "heimdall" proxy: { "host": "heimdall.lsio", "port": 80 } timeoutSeconds: 60 INFO [2021-09-11 07:09:20.163 +0200]: Proxy listening port: 80 INFO [2021-09-11 07:09:20.165 +0200]: Proxy placeholder server listening port: 8080 host: "127.0.0.1" INFO [2021-09-11 07:09:53.520 +0200]: Starting container container: "code-server" INFO [2021-09-11 07:15:11.070 +0200]: Stopping container container: "code-server"

code.domain.com works but when I try to reach home.domain.com, CN doesn’t start the homer container despite being in the same network, exact name and being stopped. Worked perfectly before the update (yesterday).

fitur commented 3 years ago

Ignore my issue. I'm stupid. CN had changed it's IP address after the update. Changed Swag to use the Docker resolver instead of a static IP.

Thanks for a really valuable project.