Minecraft Dedicated Server.
Introduction
This Docker image exists because I wanted a way to run the Windows version of the Bedrock Dedicated Server on Linux. Why would I want to do this? Because the Linux version has truly awful performance.
The image is based on Element Zero which does most of the heavy lifting with regards to making it work on Linux. It also provides mod support which I don't really need but it doesn't get in the way either.
Element Zero provides instructions for running in Docker but it has a number of manual installation steps. This image automates those steps and makes it easier to mount worlds and config into the image with some well-placed symlinks.
Usage
Create a docker-compose.yaml file with the following contents. This will use a pre-built image stored on Docker Hub. Modify /path/to/my with the location you want to persist config and world data.
version: '2.1'
services:
minecraft:
image: bretth/bedrock-server:1.16.100.04-v0.1.0-6-1
ports:
- "19132:19132/udp"
restart: always
# allow attaching to container
tty: true
stdin_open: true
volumes:
- /path/to/my/config:/data/config
- /path/to/my/worlds:/data/worldsTo build the image from source, replace image: ... with build: ..
Place your configuration files in the /path/to/my/config folder. The files and directories must be owned by a user:group of 1000:1000. This is a limitation of the base image that this image builds on. The configuration files include:
server.properties,whitelist.json, andpermissions.jsonfiles. Original copies of these files can be found in the vanilla Bedrock Dedicated Server Download.custom.yaml. Details of this file are documented on the Element Zero Wiki. If it doesn't exist, this file will be created on first startup.
Start the server via docker compose.
docker-compose up -dStop the server via docker compose.
docker-compose downAttach to the running process for the purposes of running commands.
docker attach <container-id>To detach from the process without exiting the container, use Ctrl + p, Ctrl + q.