Closed CEbbinghaus closed 2 years ago
All Errors are File IO operations which is very relevant to docker and the only possible answer to the issue I'm having.
I'm experiencing the exact same issue in my vanilla 1.18.1 server running on Docker Desktop 4.3.2 (72729) on Windows 11.
@livesinshorts Multiple people are finding file system issues on Windows 11 Docker Desktop. Those issues are beyond my control since the container ultimately runs the Minecraft Java process and gets out of the way.
@CEbbinghaus are you also running on Windows 11? If not, please clarify your host type and file systems type.
In any case, again, there is nothing I can do about these issues. I'll leave this issue open for others to find and discuss, but there's nothing I can do to work on it.
@livesinshorts I forgot to mention, please report this with Docker Desktop since it is something about the volume mapping operation. Named volumes work fine BTW.
@itzg Thank you for turning me onto this issue. Foolish of me for not digging deeper into the docker side of things first as the issues cropped up after moving this to a windows 11 host. Thanks again!
FYI #1102 is where some existing observations were made about Docker Desktop on Windows 11.
Thanks for the response. Yeah i'm running windows 11. It never occured to me that it might be docker/image that was messing up. Which ended up costing me days of troubleshooting the wrong thing. Glad this wont be an issue on the server but annoying that it caused problems on the client. Will try and keep this updated if any progress occurs on the docker side
This issue is stale because it has been open 30 days with no activity. Please add a comment describing the reason to keep this issue open.
I'm going to close this one and leave #1102 to watch for reports of progress.
Describe the problem
When running a Server via Docker these errors appear constantly on all 3 types (Paper, Fabric, Vanilla) however running the server (vanilla) on the host machine by itself works completely fine with no errors. This server is a little test for my full server running the same image on the remote that I want to upgrade.
I did some digging through the Minecraft bug pages and found a relevant Issue #161823 however this doesn't seem to be related since the world is intact apart from the Vegetation.
In the world they appear as broken Generation of the Mushrooms:
Since the terrain itself is consistent and only the mushrooms are broken it doesn't look like an issue specific to Minecraft such as the bug outlined above. It should also not be the generation since I have been able to take the same world and play it normally in survival mode. This issue seems to be pure with this image running in a container.
Initially, I only bound the world to my drive but now I'm binding all the data since that is how it's running on my server, however, there is no difference between them (both break the same way)
Container definition
Container logs
(The logs were too large so I copied all that I still had access to.)