mtoensing / Docker-Minecraft-PaperMC-Server

Starts a Minecraft PaperMC server
https://hub.docker.com/r/marctv/minecraft-papermc-server
MIT License
246 stars 92 forks source link

openjdk:17-alpine not compatible with Minecraft 1.18 due to it using the 17-ea version of Java #34

Closed ilektron closed 2 years ago

ilektron commented 2 years ago

https://github.com/mtoensing/Docker-Minecraft-PaperMC-Server/blob/cb710a7b160e81a7b41420cb5451d7dae008df05/Dockerfile#L4

Experienced a server crash due to the openjdk:17-alpine docker image not using the actual 17 release version of java at this time

mtoensing commented 2 years ago

See #33 Branch "1.18" or "beta" works fine. There is already a "1.18" image on Docker Hub:

docker pull marctv/minecraft-papermc-server:beta

Experimental test builds for 1.18. Use with extreme caution! Backups are mandatory.

ilektron commented 2 years ago

While I found it ran fine for some cases, I experienced a crash that turned out to be because the openjdk:17-alpine build uses the 17-ea version of Java which is missing some functions that were added for the actual 17 release version. The openjdk:17-alpine image is kind of in limbo right now, see http://jdk.java.net/17/

mtoensing commented 2 years ago

Do you have a better idea which base image is better? Maybe a Pull Request?

ilektron commented 2 years ago

I couldn't really find one at this time, so I built my own java docker image with version of java that Paper recommends, ilektron/paperjdk. I'll test stability today and if everything looks good I'll work on a pull request in the next day that just changes the jdk image.

mtoensing commented 2 years ago

Thanks @josxha

josxha commented 2 years ago

Hi @mtoensing, i just wanted to let you know that while the beta image on Docker hub uses now the release version of java 17, it seems that the 1.18 image still uses the incompatible early access java version.

image

See: https://hub.docker.com/layers/marctv/minecraft-papermc-server/1.18/images/sha256-1785408f5c500a76182daa93f08b73e9ad7d67d6061a7d5693ae5b41b9428af6?context=explore

mtoensing commented 2 years ago

Maybe a caching issue? It seems okay now

RuofengX commented 2 years ago

Still not work now. I am planning to use onenjdk-17 instead

mtoensing commented 2 years ago

Did you try the "latest" tag?

josxha commented 2 years ago

@RuofengX @mtoensing I agree, the image runs fine