| 03:00:04 | | mutantmonkey quits [Ping timeout: 240 seconds] |
| 03:12:48 | | mutantmonkey (mutantmonkey) joins |
| 04:08:48 | | @kiskaWee1 is now known as @kiskaWeebChat |
| 06:28:18 | | Terbium joins |
| 06:45:57 | | Matthww6 joins |
| 06:46:43 | | Matthww quits [Ping timeout: 240 seconds] |
| 06:46:44 | | Matthww6 is now known as Matthww |
| 06:59:20 | | Matthww5 joins |
| 07:00:03 | | Matthww quits [Ping timeout: 240 seconds] |
| 07:00:04 | | Matthww5 is now known as Matthww |
| 14:16:04 | | Arcorann quits [Ping timeout: 265 seconds] |
| 18:07:35 | | Matthww quits [Ping timeout: 265 seconds] |
| 18:11:41 | | Matthww joins |
| 18:36:11 | | VADemon joins |
| 21:54:14 | <atphoenix> | The 'docker stop' options include a time parameter that allows us to have a better chance of cleanly stopping a project worker via SIGTERM before a possible later SIGKILL. I do not see a way to configure Watchtower to have a delay between SIGTERM and SIGKILL when it comes to automatically updating workers. https://docs.docker.com/engine/reference/commandline/stop/ and https://containrrr.dev/watchtower/stop-signals/ |
| 21:57:02 | <atphoenix> | If I want to have docker to only try a 'SIGTERM' stop, and never to fall back to SIGKILL, is 'docker kill --signal=SIGTERM my_container' the correct approach? https://docs.docker.com/engine/reference/commandline/kill/#send-a-custom-signal--to-a-container |
| 22:08:36 | | Arcorann (Arcorann) joins |