-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to start Minecraft Server in Docker #3048
Comments
Is this the relevant problem?
|
ATM9 used to work at least, but maybe there's new client mod exclusions needed with newest modpack. Speaking of which, be sure to re-pull the image to ensure latest global exclusions are used and temporarily set env var |
I'm giving that a try with |
|
Even after making sure all of the packages have updated, I'm having no luck. This is a brand new install. IDK what's going wrong here. It just does the very long server load process and gives up at some point. |
Yes, it's a modpack so it will have a fairly long startup time. You cancelled it manually so I can't say what the problem is other than don't stop it 😄 |
I didn't cancel it manually at all. Okay this time I disconnected the client from the hosting machine altogether so there's no possible way anything can be interpreted as a keypress. This time if it gets interrupted, it's the container itself. (It was the container itself before but I'm removing a variable just to humor you.) |
🤷 just going off of your provided logs
|
I think it got further that time. |
Nothing was connected to the machine. No keyboard or anything like that.
So weird. |
"Killed" indication means something at operating system level killed it. Thats different than the manual stop I mentioned earlier. |
You haven't mentioned any time frame for the startup so as a guess perhaps health check timeout needs to be adjusted https://docker-minecraft-server.readthedocs.io/en/latest/misc/healthcheck/ |
Yeah that sounds promising. I'll look into it! Thanks! |
Okay another failure... hmm... this time it was only a few minutes
my
|
Yeah it only gets through about |
Maybe it's this JSON file?
|
You might need to look at logs like this to see why the system is killing the container process https://docs.docker.com/engine/daemon/logs/ I'm running out of ideas 😬 |
Interesting. Maybe Docker for Windows 11 is having more issues than a linux host usually would. |
I have the same starting issue with Linux server. |
So I have the same "error message". However I am getting it later. Startup is fine but at some point whilst playing (usually between 5 to 30 minutes after startup) the above mentioned "Killed" message comes. Used compose file:
I am running Docker on a linux machine however so I think this is not a Windows problem. journalctl -xu docker.service
Log without error (before these messages there was no message for a long time - game running all fine)
|
if you are using docker desktop it has a separate settings menu for memory if its below how much you told jvm that it can use it will exit with code 137 |
did the trick for me |
Describe the problem
The error is in this file:
2024-08-23-output.log.txt
Basically it errors out while trying to spin up for the first time.
Container definition
Container logs
2024-08-23-output.log.txt
The text was updated successfully, but these errors were encountered: