| 09:47:24 | | Arcorann quits [Ping timeout: 240 seconds] |
| 09:50:19 | | Arcorann (Arcorann) joins |
| 14:48:24 | | Arcorann quits [Ping timeout: 240 seconds] |
| 19:47:06 | | DogsRNice (Webuser299) joins |
| 21:23:12 | <atphoenix> | upon further experimentation, and the use of 'docker events' to monitor the signals, it turns out 'docker stop' is sending a SIGINT (2) and not a SIGTERM (15). The docker docs say it sends a SIGTERM. Oh well. |
| 21:24:53 | <atphoenix> | as such, this command worked to cleanly stop a container, and unlike 'docker stop -t ####', it doesn't use a grace period before switching to a hard kill: sudo docker kill --signal=SIGINT archiveteam |
| 21:39:55 | <atphoenix> | that wasn't worded well. 'docker stop -t ####' uses a grace period of #### seconds as specified by -t before switching to hard kill. |
| 21:40:21 | <atphoenix> | 'docker kill --signal=SIGINT archiveteam' sends the SIGINT signal, and that's all it does. It doesn't try to hard kill. |