question for linuxgsm/root user, and custom crontab
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, docker-compose, shell
- Domain
- devops, infrastructure
Research direction
Start with the docker-compose minecraft service, its mounted /data volume, and the custom crontab commands shown in the report. Trace how the linuxgsm user and root resolve the /app/mcserver configuration, then verify whether scheduled commands run and persist after a container restart.
Written by the indexing model from the issue text.
Description
hello everyone,
i try to use custom crontab in linuxgsm user, and i find out it will restore to default if i restart container, and even before restart container, the crontab will not work as expected, like no run the command
here is the crontab
*/60 * * * * /app/mcserver update > /dev/null 2>&1
0 * * * * /app/mcserver send "kill @e[type=item]"
and then i try to set up crontab in root user like this
0 * * * * su - linuxgsm -c '/app/mcserver send "kill @e[type=item]"'
it can't run either.
when i run command alone, its show "server not running".
then i type
su - linuxgsm -c '/app/mcserver dt'
seems its wrong config file path. maybe its environment problem? but i check the 'env' in linuxgsm user and root user, its the same.
here is my docker-compose
minecraft:
image: gameservermanagers/gameserver:mc
container_name: minecraft
volumes:
- /mnt/ssd/docker/minecraft:/data
network_mode: host
restart: always
any idea for it ?
- Dominant language
- Shell
- Stars
- 347
- Forks
- 26
- Avg merge
- 8h 2m
- Merged PRs (30d)
- 2
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GameServerManagers/docker-gameserver
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
GameServerManagers/docker-gameserver#144 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
GameServerManagers/docker-gameserver#142 · 2 comments ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
GameServerManagers/docker-gameserver#113 · 1 comment ·
All issues in GameServerManagers/docker-gameserver
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
varnish/helm-varnish#173 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
GameServerManagers/LinuxGSM#5242 ·
Maintainers usually reply within 1 day
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days