Add exit call to kill command

[MattyTheHacker]

No description provided.

[CarrotManMatt]

Do you have a link to the documentation that shows that exiting with exit code 0 will tell docker not to do a restart?

[MattyTheHacker]

Do you have a link to the documentation that shows that exiting with exit code 0 will tell docker not to do a restart?

nah - but we're set to "Always" which says that if it's manually shut down it won't attempt to restart. The "on-failure" config option says it considers an error to be a non-zero exit code so assumed 🤷 don't ask me shit like this as if I have any idea what I'm doing lmfao /lh

fwiw: https://docs.docker.com/config/containers/start-containers-automatically/

[CarrotManMatt]

Cheers, that's the correct link. Yh it's a shame the config options for restart policies aren't perfect. Using on-failure would be useful as it would seem to solve the problem, except for the fact that it won't restart if the docker Daemon goes down.

[CarrotManMatt]

Although considering the likelihoods of TeX-Bot dieing Vs the hetzner server dieing I think one is much more likely than the other, so maybe changing the docker restart policy on all deployments to be on_failure would be a good idea.

[CarrotManMatt]

Merging this PR will require any deployments to have their docker restart policy set to on-failure.

[MattyTheHacker]

Appears to be intended functionality - but just as an fyi

[CarrotManMatt]

Appears to be intended functionality - but just as an fyi

Yh I spent ages trying to figure out why that was suddenly appearing. I'm certain it is from py-cord internals not shutting down correctly, so cannot be helped by us. It is still peculiar that it has only just started to occur though.