The default cronjob update does not restart the server (but a manual one does???)

[WildPenquin]

Hi,

For some reason the default cronjob does update the server, but does not restart it (as it should).

I've created an upstream issue here: GameServerManagers/LinuxGSM#4598 - but realized the issue is more likely caused by the docker image.

I had actually disabled the cronjob previously, and run my cronjob much less seldomly (I don't want restarts for minor updates during playtime) trough cron outside the container. For some reason an update run this way does trigger the restart of the server. But an update (?) of the docker image caused the default cronjob to re-install.

I'm also using podman (for a more secure, rootless container setup than which docker can do at the moment), and the update is run like this: podman exec -ti --user linuxgsm $CONTNAME /app/pmcserver u - but this indeed works correctly, or used to. I need to wait for another update to be available until I can check for sure.

Possibly related: #39

[WildPenquin]

Today, a new papermc server was released and this was a great opportunity to test! So I re-enabled the default hourly cronjob:

*/60 * * * * /app/pmcserver update > /dev/null 2>&1

And sure enough, I can see the server got updated but not restarted!

I've tested in the interim with a daily regular cronjob outside the container, which effectively runs this (of course $CONTUSER and $CONTNAME set appropriately):

podman exec -ti --user $CONTUSER $CONTNAME /app/pmcserver u

does work properly, i.e. updates and restarts the server.

I could make a test-case (and image which is outdated) for testing purposes.