[Bug]: Docker already has an entry in Crontab

[ben-2357]

User story

I want the crontab entry to be removed so users are able to set their own wihtout having to remove/comment it out every time the container is restarted.

Game

PaperMC

Linux distro

Ubuntu 22.04

Command

command: update

Further information

There is a cron entry in the container by default:

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

I don't know if this is intentional, but it is very annoying because I'd like to set my own update interval without having to modify the actual application code. I didn't think it was necessary to make an issue for such a small problem. Thanks!

Relevant log output

No response

Steps to reproduce

1. Use the container lol

[zuedev]

Which image are you using? I couldn't find any cron entries on the latest GHCR build.

[ben-2357]

Maybe it's because I'm using the Docker Hub image?:

services:
  linuxgsm-pmc-bind:
    image: gameservermanagers/gameserver:pmc
    # image: ghcr.io/gameservermanagers/gameserver:pmc

Here's a video showing the latest image.

[zuedev]

Never mind, you're right! I was entering the container without specifying the linuxgsm user.

I agree that having only the docker images preconfigured to update every hour is pretty weird.

I've made a PR for this, hopefully it gets merged!

[WildPenquin]

I was certain there are other crontab -related issues already, and there are. At least #4584 and #4508 . IIRC I've seen some discussion in another issue somewhere but can not find it ATM (EDIT: realized the latter has nothing to do with the docker images per se). I'm mentioning these here so that everyone is up to date on the feature / issues and pull requests, so that perhaps a common fix can be found.

I agree the default crontab entry needs to go. It is intrusive, as it interrupts gameplay on servers which do not need to be on the bleeding edge and get frequent updates. The users should decide. Currently, I run 'crontab -r' after each reboot and update of the image, but I feel I should not need to.

[romanvoloboev]

any updates on this?? I don't want my server suddenly start autoupdate at the pick online!

[WildPenquin]

I've realized one can set UPDATE_CHECK=0. This is not documented (AFAIK), but will skip creating the crontab on every restart of the container (or set it to some other value if want something else than hourly checks).

I've brewed an implementation for a persistent crontab within the container.