Legendary Minecraft Bedrock Container

Minecraft Bedrock Docker Edition
Minecraft Bedrock Docker Edition

I’ve been getting asked to put this together for years including in official GitHub issues. I always knew it would be a great idea but it turned out even better than I expected. This image works great on all platforms including Raspberry Pi!

This is based off my Minecraft Bedrock Linux Dedicated Server scripts for Linux project. I’m going to release a version for the Java Minecraft edition as well so stay tuned for that.

The official GitHub repository is located here.

The official Docker Hub repository is located here.

If you are looking for the Java version of the Docker container it is located here. This is for the Bedrock edition of Minecraft.

You can also run my Geyser + Floodgate Java Minecraft Server container and Bedrock players will be able to connect to it!

Features

  • Sets up the official Minecraft Bedrock Server (currently in alpha testing)
  • Fully operational Minecraft Bedrock edition server in a couple of minutes
  • Adds logging with timestamps to “logs” directory
  • Multiarch Support – all Docker platforms supported including Raspberry Pi
  • Automatic backups when container/server restarts
  • Supports multiple instances — you can run multiple Bedrock servers on the same system
  • Updates automatically to the latest or user-defined version when server is started
  • Files stored in named Docker volume allowing for extremely easy access/editing and leveraging more advanced Docker features such as automatic volume backups
  • *NEW* – Box64 support added for improved speeds on aarch64 (ARM 64 bit)

Usage

First you must create a named Docker volume. This can be done with:

docker volume create yourvolumename

Now you may launch the server and open the ports necessary with one of the following Docker launch commands.

With default ports:

docker run -it -v yourvolumename:/minecraft -p 19132:19132/udp -p 19132:19132 -p 19133:19133/udp -p 19133:19133 05jchambers/legendary-bedrock-container:latest

With custom ports:

docker run -it -v yourvolumename:/minecraft -p 12345:12345/udp -p 12345:12345 -p 12346:12346/udp -p 12346:12346 -e PortIPV4=12345 -e PortIPV6=12346 05jchambers/legendary-bedrock-container:latest

IPV4 only:

docker run -it -v yourvolumename:/minecraft -p 19132:19132/udp -p 19132:19132 05jchambers/legendary-bedrock-container:latest

Configuration / Accessing Server Files

The server data is stored where Docker stores your volumes. This is typically a folder on the host OS that is shared and mounted with the container. I’ll give the usual locations here but if you’re having trouble just do some Googling for your exact platform and you should find where Docker is storing the volume files.

You can find your exact path by typing:

docker volume inspect yourvolumename

This will give you the fully qualified path to your volume like this:

{
        "CreatedAt": "2022-05-09T21:08:34-06:00",
        "Driver": "local",
        "Labels": {},
        "Mountpoint": "/var/lib/docker/volumes/yourvolumename/_data",
        "Name": "yourvolumename",
        "Options": {},
        "Scope": "local"
}

On Linux it’s typically available at:

/var/lib/docker/volumes/yourvolumename/_data

On Windows it’s at

C:\ProgramData\DockerDesktop

but may be located at something more like

\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes\

if you are using WSL (Windows Subsystem for Linux).



On Mac it’s typically

~/Library/Containers/com.docker.docker/Data/vms/0/

If you are using Docker Desktop on Mac then you need to access the Docker VM with the following command first:

screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty

You can then normally access the Docker volumes using the path you found in the first step with docker volume inspect

Most people will want to edit server.properties. You can make the changes to the file and then restart the container to make them effective.

Backups are stored in the “backups” folder

Log files with timestamps are stored in the “logs” folder.

Version Override

In some scenarios you may want to run a specific version of the Bedrock server. That is now possible by using the “Version” environment variable:

-e Version=1.18.33.02

For example:

docker run -it -v yourvolumename:/minecraft -e Version=1.18.33.02 -p 19132:19132/udp -p 19132:19132 05jchambers/legendary-bedrock-container:latest

This is useful if Microsoft hasn’t released versions of the client and dedicated server at the same time so you can match whichever version your players can connect with.

Clean Environment Variable

If the server is having trouble starting you can clean the downloads folder and force reinstallation of the latest version like this:

docker run -it -v yourvolumename:/minecraft -e Clean=Y -p 19132:19132/udp -p 19132:19132 05jchambers/legendary-bedrock-container:latest

This is useful if a download corrupted or something modified your container contents as it will clear everything out and reinstall the latest Bedrock server fresh.

Disable Box64 (aarch64 only):

If you are having trouble running the dedicated server with Box64 support you can tell it to use QEMU instead with:

-e UseQEMU=Y

For example:

docker run -it -v yourvolumename:/minecraft -e UseQEMU=Y -p 19132:19132/udp -p 19132:19132 05jchambers/legendary-bedrock-container:latest

Troubleshooting Note – Oracle Virtual Machines

A very common problem people have with the Oracle Virtual Machine tutorials out there that typically show you how to use a free VM is that the VM is much more difficult to configure than just about any other product / offering out there.

It is because there are several steps you need to take to open the ports on the Oracle VM. You need to both:

  • Set the ingress ports (TCP/UDP) in the Virtual Cloud Network (VCN) security list
  • *and* set the ingress ports in a Network Security Group assigned to your instance

Both of these settings are typically required before you will be able to connect to your VM instance. This is purely configuration related and has nothing to do with the script or the Minecraft server itself.

I do not recommend this platform due to the configuration difficulty but the people who have gone through the pain of configuring an Oracle VM have had good experiences with it after that point. Just keep in mind it’s going to be a rough ride through the configuration for most people.

Troubleshooting Note – Hyper-V

There is a weird bug in Hyper-V that breaks UDP connections on the Minecraft server. The fix for this is that you have to use a Generation 1 VM with the Legacy LAN network driver.

Additional Support

The comments section right here is the best place for support. The second best place is the GitHub issues section.

I will add additional documentation based on what problems people are running into / questions people are asking because right now I’m not really sure what those will be yet. Definitely let me know if you need any of these things!

guest

59 Comments
Inline Feedbacks
View all comments

MC_DAVE
MC_DAVE
14 days ago

how do you manage backups in the docker ?

Justin
Justin
26 days ago

All glory to James
My build:
Dell Wyse 5070 Thin Client Install (Pentium)
Install Ubuntu Server 22.04 LTS on device including SSH (Named:wyseserver)

1. Use Putty from windows machine to connect to wyseserver
2. Install updates: sudo apt update && sudo apt upgrade -y && sudo apt autoremove -y
3. Reboot: reboot
4. Fix any issues with updates:
sudo apt --fix-broken install
5. Install docker: sudo curl -fsSL get.docker.com | sh
6. Create volume for portainer (portainer pretty kewl but not required) :
docker volume create portainer_data
7. Install portainer: docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest
8. Install NFS so I can access the data from my Windows computer (PS install the Service for NFS features on Windows machine and don’t forget to start the service when done):
sudo apt install nfs-kernel-server
9. Enable the NFS Service to start when server starts:
sudo systemctl enable nfs-kernel-server.service
10. Start the NFS Service:
sudo systemctl start nfs-kernel-server.service
11. Make some directories for a few persisten volumes for the data for the docker containers (make as many as you need servers):
sudo mkdir -p /mnt/dvols/mcsvol01
sudo mkdir -p /mnt/dvols/mcsvol02
sudo mkdir -p /mnt/dvols/mcsvol03

12. Give nobody and nogroup permissions to these folders:
sudo chown -R nobody:nogroup /mnt/dvols/mcsvol01
sudo chown -R nobody:nogroup /mnt/dvols/mcsvol02
sudo chown -R nobody:nogroup /mnt/dvols/mcsvol03

13. Give read write permissions to these folders:
sudo chmod 777 /mnt/dvols/mcsvol01
sudo chmod 777 /mnt/dvols/mcsvol02
sudo chmod 777 /mnt/dvols/mcsvol03

14. Now give access to a specific ip or range to these NFSs:
sudo nano /etc/exports
Enter the IP or Range or subnet of the machine that you use to access the NFS
/mnt/dvols/mcsvol01 192.168.0.0/24(rw,sync,no_subtree_check)
/mnt/dvols/mcsvol02 192.168.0.0/24(rw,sync,no_subtree_check)
/mnt/dvols/mcsvol03 192.168.0.0/24(rw,sync,no_subtree_check)

15. Save the File: Ctrl+X,Y,Enter
16. Update the NFS Table:
sudo exportfs -a
17. Restart the NFS SerVice:
sudo systemctl restart nfs-kernel-server
18. Check the status of the service if you are so inclined (absolutely optional):
sudo -i
systemctl status nfs-kernel-server
exit

19. Allow NFS through firewall from specific IP:
sudo ufw allow from 192.168.0.0/24 to any port nfs
20. Create some persistent docker volumes and bind them to the folders we created earlier (make as many as you need servers):
docker volume create --driver local --opt type=none --opt o=bind --opt device=/mnt/dvols/mcsvol01 mcserver01vol
docker volume create --driver local --opt type=none --opt o=bind --opt device=/mnt/dvols/mcsvol02 mcserver02vol
docker volume create --driver local --opt type=none --opt o=bind --opt device=/mnt/dvols/mcsvol03 mcserver03vol

21. Create the servers (again as many as you need) (my ports follow sequence 19 server# 2/3):
docker run -it -v mcserver01vol:/minecraft --name mcserver01 --restart=always -e NoScreen=Y -e TZ="Australia/Sydney" -p 19012:19012/udp -p 19012:19012 -p 19013:19013/udp -p 19013:19013 -e PortIPV4=19012 -e PortIPV6=19013 05jchambers/legendary-bedrock-container:latest
docker run -it -v mcserver02vol:/minecraft --name mcserver02 --restart=always -e NoScreen=Y -e TZ="Australia/Sydney" -p 19022:19022/udp -p 19022:19022 -p 19023:19023/udp -p 19023:19023 -e PortIPV4=19022 -e PortIPV6=19023 05jchambers/legendary-bedrock-container:latest
docker run -it -v mcserver03vol:/minecraft --name mcserver03 --restart=always -e NoScreen=Y -e TZ="Australia/Sydney" -p 19032:19032/udp -p 19032:19032 -p 19033:19033/udp -p 19033:19033 -e PortIPV4=19032 -e PortIPV6=19033 05jchambers/legendary-bedrock-container:latest

22. Going to stop the first server so I can copy in my worlds, edit properties, textures so on…:
docker stop mcserver01
23. Make permissions nobody and nogroup so I can edit the contents:
sudo chown -R nobody:nogroup /mnt/dvols/mcsvol01
24. Navigate to folder from my windows PC and do all changes I require.
\\wyseserver\mnt\dvols\mcsvol01
25. Start Docker contrainer up again as complete with my changes (I’m assuming the fixpermissions.sh is run on startup James?):
docker start mcserver01
26. Access the terminal of the docker container:
docker exec -it mcserver01 bash
28. Run the fix permissions script if required (Again not sure if required James?)
cd scripts
./fixpermissions.sh

29. Exit the docker container terminal safely:
Ctrl+P+Q

Moses
Moses
1 month ago

Hello James!

This Docker version worked really good! Thank you for this! 😀

However i noticed something that i couldn’t manage to figure out.
How do we access the terminal of the server itself?
I wanted to give character admin role by writing “/OP [name]”

But i can’t seem to figure out how and where to even start the server again after we reboot our Raspberry pi 🙁

Moses
Moses
1 month ago
Reply to  jamesachambers

Hi again James!

Thank you i finally got it to work! 🙂

I can’t however connect to my server after I rebooted my Pi today. All i get is “Could not connect: Outdated Client!”
comment image

Do you know how we can fix this? 🙁

Sudîmia
Sudîmia
1 month ago

Hello, I think what you’re doing is really cool and the fact that you somehow managed to make this work on ARM even though Microsoft didn’t make an Arm build of their own server software (kinda dumb considering you can host a world on an ARM device so it’s obviously possible, I’ve even installed lineage OS and tested Bedrock on this Pi, though the gpu didn’t like that very much). Unfortunately I’ve been having trouble whenever I try to run the server it comes up with some errors and then it says:

Unable to connect to update website (internet connection may be down). Skipping update ...

Even though I can pull the latest version without issue. It then says “Starting Minecraft server…” and terminates instantly with no explanation. I noticed another commentor had this issue as well but you made an updated version to fix that issue and it worked for them, so I have no idea why it’s happening, unless it’s possibly a different problem causing the same outcome. I haven’t actually been able to start the server once, it’s done the same thing since I started following your tutorial. I tried apt update and apt upgrade to make sure everything was up to date as well, nothing changed.

On top of that, I am unable to access the docker volume as it supposedly doesn’t exist (sudo docker volume inspect minecraftbedrockserver returns /var/lib/docker/volumes/minecraftbedrockserver/_data as the Mount point) and the /var/lib/docker folder is empty and is 0 bytes in size so there doesn’t seem to be anything in it.

Using a Raspberry Pi 4, 4gb with 32-bit version of Raspberry Pi OS

Screenshot of output from command line: https://postimg.cc/gxVM6H87

Output copied from commandline:

pi@raspberrypi:~ $ sudo docker run -it -v minecraftbedrockserver:/minecraft -p 19132:19132/udp -p 19132:19132 05jchambers/legendary-bedrock-container:latest
Minecraft Bedrock Server Docker script by James A. Chambers
Latest version always at https://github.com/TheRemote/Legendary-Bedrock-Container
Don't forget to set up port forwarding on your router! The default port is 19132
Ports used - IPV4: 19132 - IPV6: 19133
sudo: unable to get time of day: Operation not permitted
sudo: error initializing audit plugin sudoers_audit
Checking for the latest version of Minecraft Bedrock server ...
Unable to connect to update website (internet connection may be down). Skipping update ...
Starting Minecraft server...

[screen is terminating]

pi@raspberrypi:~ $ sudo docker pull 05jchambers/legendary-bedrock-container:latest
latest: Pulling from 05jchambers/legendary-bedrock-container
Status: Image is up to date for 05jchambers/legendary-bedrock-container:latest
docker.io/05jchambers/legendary-bedrock-container:latest

pi@raspberrypi:~ $ sudo docker run -it -v minecraftbedrockserver:/minecraft -p 19132:19132/udp -p 19132:19132 05jchambers/legendary-bedrock-container:latest
Minecraft Bedrock Server Docker script by James A. Chambers
Latest version always at https://github.com/TheRemote/Legendary-Bedrock-Container
Don't forget to set up port forwarding on your router! The default port is 19132
Ports used - IPV4: 19132 - IPV6: 19133
sudo: unable to get time of day: Operation not permitted
sudo: error initializing audit plugin sudoers_audit
Checking for the latest version of Minecraft Bedrock server ...
Unable to connect to update website (internet connection may be down). Skipping update ...
Starting Minecraft server...

[screen is terminating]

Sudîmia
Sudîmia
1 month ago
Reply to  jamesachambers

Wow that was fast! Thank you, that makes sense because this pi had been unused for about a year. Will reimage it with the 64-bit version of Bullseye and get back to you in case it might help someone else with the same issue.

Sudîmia
Sudîmia
1 month ago
Reply to  jamesachambers

So I reimaged the Pi with Bullseye 64-bit and re-did everything from scratch including a mumble server and smb server, as well as installing box64, and then set up your docker container. I got no errors and was able to join without issue. The first join took about a minute or two (pi was generating the nearby chunks) everything seemed normal, there were animals as well. After the initial generation it took about 30-45 seconds to join.

I didn’t notice much lag though the first command entered on either the server CLI or on an operator client seems to always produce a giant lag spike and everything in the game freezes for about 30-60 seconds and then it’s suddenly fine. Teleporting to unloaded chunks seems to do the same thing as well, though I didn’t do a lot of testing. I do believe most of the problems can be a attributed to lack of an SSD or other decent storage options, current storage is a 200gb micro SD card. I imported a creative world to the docker volume and used that for the server and noticed some lag with pressure plates connected to iron doors and would end up walking into the door before it opened.

Planning on using a faster storage option in the future, though I’m not sure how I would move a docker volume to a different drive it’s probably pretty easy. This seems like a viable solution and would work fine for a dedicated Bedrock server when using a faster storage device. Amazing work!

Kerzenmeister
Kerzenmeister
2 months ago

Hey James,

at first I’d like to thank you to make it so easy to set up a minecraft server on a raspberry for us! Great work. But I still run into a bit of trouble. I am using a Raspberry Pi 4 with 4 GB of ram and a Raspberry Pi OS (64 bit). The Server starts perfectly fine and delivers the following output:

[2022-07-21 14:49:31] NO LOG FILE! - setting up server logging...
[2022-07-21 14:49:31] [2022-07-21 14:49:31:612 INFO] Starting Server
[2022-07-21 14:49:31] [2022-07-21 14:49:31:616 INFO] Version 1.19.10.03
[2022-07-21 14:49:31] [2022-07-21 14:49:31:616 INFO] Session ID 779e793e-60db-408f-a088-9e9bf9d4c61e
[2022-07-21 14:49:31] [2022-07-21 14:49:31:655 INFO] Level Name: Bedrock level
[2022-07-21 14:49:32] [2022-07-21 14:49:32:710 INFO] Game mode: 0 Survival
[2022-07-21 14:49:32] [2022-07-21 14:49:32:711 INFO] Difficulty: 1 EASY
[2022-07-21 14:49:33] [2022-07-21 14:49:33:119 INFO] opening worlds/Bedrock level/db
[2022-07-21 14:50:05] [2022-07-21 14:50:05:540 INFO] IPv4 supported, port: 19132
[2022-07-21 14:50:05] [2022-07-21 14:50:05:550 INFO] IPv6 not supported
[2022-07-21 14:50:15] [2022-07-21 14:50:15:798 INFO] Server started.
[2022-07-21 14:50:15] [2022-07-21 14:50:15:858 INFO] ================ TELEMETRY MESSAGE ===================
[2022-07-21 14:50:15] [2022-07-21 14:50:15:858 INFO] Server Telemetry is currently not enabled.
[2022-07-21 14:50:15] [2022-07-21 14:50:15:859 INFO] Enabling this telemetry helps us improve the game.
[2022-07-21 14:50:15] [2022-07-21 14:50:15:860 INFO]
[2022-07-21 14:50:15] [2022-07-21 14:50:15:863 INFO] To enable this feature, add the line 'emit-server-telemetry=true'
[2022-07-21 14:50:15] [2022-07-21 14:50:15:864 INFO] to the server.properties file in the handheld/src-server directory
[2022-07-21 14:50:15] [2022-07-21 14:50:15:866 INFO] ======================================================
[2022-07-21 14:50:15] [2022-07-21 14:50:15:013 INFO] IPv4 supported, port: 46660
[2022-07-21 14:50:15] [2022-07-21 14:50:15:013 INFO] IPv6 not supported
[2022-07-21 14:50:31] [2022-07-21 14:50:31:429 INFO] Player connected: XXXXX, xuid: 2535450906092014

I am using a Huwai MediaPad M5 lite 10 with Android 8 and Minecraft 1.19.10 to connect to the server. When connecting it gets stuck at “searching for server” for 2 minutes and 50 seconds until I join the game. The game than starts in an ice biome and works fine at the spawning point. But when I walk away a few chunks the next chunks just won’t load. I am trapped in quite a tiny world. Is there any known reason why it takes so long to join the world or why it is not loading within an acceptable amount of time?

Any hint is appreciated. My boys would love to play on this server 😉

I thank you for your efforts in advance.

Kind regards

Kerzenmeister from Germany

Kerzenmeister
Kerzenmeister
2 months ago
Reply to  jamesachambers

Thank you so much James,

I benchmarked my Sandisk Ultra with a score of 1352. I will certainly follow your instructions with a modest overclocking and a fast SSD. I thank you so much for your instructions and the time and effort you are spending for the community.

Kind regards

Kerzenmeister

kerzenmeister
kerzenmeister
2 months ago
Reply to  jamesachambers

Hello James,

things have improved significantly thanks to your hints. The benchmark now shows the following:

Category Test Result
HDParm Disk Read 327.14 MB/s
HDParm Cached Disk Read 316.94 MB/s
DD Disk Write 125 MB/s
FIO 4k random read 17793 IOPS (71172 KB/s)
FIO 4k random write 11844 IOPS (47379 KB/s)
IOZone 4k read 33680 KB/s
IOZone 4k write 29672 KB/s
IOZone 4k random read 18338 KB/s
IOZone 4k random write 32107 KB/s

Score: 7753

Unfortunately the world still loads slow but a lot faster with the newly installed Samsung SSD. It still takes about 2 minutes and 40 seconds to join the server. I’ll use it anyway since nukkit for instance lacks of recieps. Hopefully my sons will accept it ;-). Thank you so much for your hard work to make using the Raspberry Pi as a server more user friendly. Highly appreciated. I’ll have a look at this page from time to time to watch your improvements.

Kind regards from Germany

Kerzenmeister