dae5a097e9
A deploy was running the same max ram for both the pod and the java app. This led to issues where the java app would use its max ram and the pod would think it was out of memory. It would kill the pod and the minecraft server with it, often not saving the last few minutes of progress. Now the deploy runs 1GiB extra ram than the java app.
Minecraft
Getting server.jar
Running Locally
docker-compose build minecraft
docker-compose up minecraft
Uploading to Docker Hub
In docker-compose.yaml, update the image tag to:
...
services:
minecraft:
build: .
image: <your_username>/minecraft:<version>-1
ports:
...
then run
docker-compose push
Running in kubernetes
In k8s/deploy.yaml, edit the deploy
...
spec:
containers:
- name: minecraft
image: <your image from above>
ports:
...
Then run the following
kubectl apply -f k8s/pvc
kubectl apply -f k8s
Your minecraft server will be available on port 25565
Create a Backup
kubectl cp <pod_name>:/mc_data <backup>
Restore from Backup
kubectl cp <backup> <pod_name>:/mc_data
Cool seeds
7485786574821478084
Spawns you next to a nether portal with golden axe and pickaxe. River and Village close by.
-8018833100564192815
Use with an amplified world, massive island