You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to get this working running on Windows 10 as the host. I've tried it with your image, and created one of my own, and I get the same error anytime I use volume to load the worlds (it works fine if I create a new world inside the container, but then obviously I would lose the world when the container closes).
I've tried minecraft is version 1.8.1.2 and 1.8.0.24 as well. I can run the 1.8.0.24 server locally outside of docker and it loads the worlds fine as well.
It works fine if the world files are local, but when I try and use an external volume for the world files it seems to crash. This happens even if it's a brand new world. It creates some files (so I know it's not a permissions issue) below when no world is specified:
Oh, and I've tried running it in Windows Subsystem for Linux, with a symbolic link for the "worlds" directory and that runs fine too. Really tearing my hair out :(
Hi
I'm trying to get this working running on Windows 10 as the host. I've tried it with your image, and created one of my own, and I get the same error anytime I use volume to load the worlds (it works fine if I create a new world inside the container, but then obviously I would lose the world when the container closes).
I've tried minecraft is version 1.8.1.2 and 1.8.0.24 as well. I can run the 1.8.0.24 server locally outside of docker and it loads the worlds fine as well.
It works fine if the world files are local, but when I try and use an external volume for the world files it seems to crash. This happens even if it's a brand new world. It creates some files (so I know it's not a permissions issue) below when no world is specified:
Bedrock world/db/000006.log (0kb)
Bedrock world/db/CURRENT (1kb)
Bedrock world/db/LOCK (0kb)
Bedrock world/db/MANIFEST-000001 (1kb)
Bedrock world/db/lost/00003.log (0kb)
Bedrock world/db/lost/MANIFEST-000001 (1kb)
I run the container as so:
docker run --network=host --name=minecraft --volume=/C/Docker/Minecraft/worlds:/bedrock-server/worlds minecraft
The output from the container is as follow:
NO LOG FILE! - setting up server logging...
NO LOG FILE! - [2019-01-18 18:55:46 INFO] Starting Server
NO LOG FILE! - [2019-01-18 18:55:46 INFO] Version 1.8.1.2
[2019-01-18 18:55:46 INFO] Level Name: Bedrock level
[2019-01-18 18:55:46 INFO] Game mode: 0 Survival
[2019-01-18 18:55:46 INFO] Difficulty: 1 EASY
[2019-01-18 18:55:48 ERROR] Fatal error when loading level data, stopping server...
Quit correctly
If I delete the above world files and run again then they are just recreated.
The only reference I've found to this issue is on the Mojang bug tracker, but there doesn't look to be an easy solution?
https://bugs.mojang.com/browse/BDS-211
The text was updated successfully, but these errors were encountered: