itzg / itzg/docker-minecraft-bedrock-server

Creating server on rancher getting crashreporter key and crash then code

Open
#120 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
1.9k
Forks
303
Avg merge
2h 26m
Merged PRs (30d)
2

Description

Im trying to launch a server on my rancher node. (rancher uses kubernetes)
When I try to launch the container I get:`CrashLoopBackOff: back-off 20s restarting failed container=minecraft-win10 pod=minecraft-win10-7487d89fc7-zkkrz_default(c18bb49c-abc3-4f6c-bd02-dd4ce557f577)`

My container logs are:

> [0000] Using /data to match uid and gid
[0000] Resolved 1000 from environment variable UID
[0000] Resolved 1000 from environment variable GID
Starting Bedrock server...
NO LOG FILE! - setting up server logging...
[2020-12-13 00:11:36 INFO] Starting Server
[2020-12-13 00:11:36 INFO] Version 1.16.200.2
[2020-12-13 00:11:36 INFO] Session ID 817e0b1d-c152-43d1-90e6-cfa43e1d8709
[2020-12-13 00:11:36 INFO] Level Name: original
[2020-12-13 00:11:36 INFO] Game mode: 0 Survival
[2020-12-13 00:11:36 INFO] Difficulty: 2 NORMAL
[INFO] opening worlds/original/db
[INFO] IPv4 supported, port: 0
[INFO] IPv6 supported, port: 0
[INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.16.200.2
OS: Linux
Server start: 2020-12-13 00:11:36 UTC
Dmp timestamp: 2020-12-13 00:11:42 UTC
Upload Date: 2020-12-13 00:11:42 UTC
Session ID: 817e0b1d-c152-43d1-90e6-cfa43e1d8709
Commit hash:
Build id: development
CrashReporter Key: 2bbd1229-24d1-3bed-9491-d58cead4b903

> Crash
[INFO]
36b8e5aa-a547-4dfd-8a78-764dc673af0e

My environment variables are:

ALLOW_CHEATS-false
DEFAULT_PLAYER_PERMISSION_LEVEL-member
DIFFICULTY-normal
EULA-TRUE
GAMEMODE-survival
GID-1000 (found with command id)
LEVEL_NAME-original
LEVEL_TYPE-DEFAULT
ONLINE_MODE-true
SERVER_NAME-Trevor
SERVER_PORT-19132
SERVER_PORT_V6-19132
TEXTUREPACK_REQUIRED-false
UID-1000
VERSION-latest

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the Rancher/Kubernetes deployment configuration and the provided container logs, including the environment variables and CrashLoopBackOff details. Reproduce the launch if possible and determine the cause of the Bedrock server crash; done means the container starts successfully under the reported configuration or the missing prerequisite is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, kubernetes, shell
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.