docker-minecraft-server: Failed to download Paper 1.16 ????

edit: yeah this would be trivial (for paper at least)

Yes, it would be trivial (and PRs are welcome BTW); however, I was hesitant to have the meaning of VERSION=LATEST differ from the primary semantic of “latest mainline/official version” to “if paper, then LATEST is actually the latest version available for Paper”.

If I can get some thumbs up/down votes on that conditional behavior, then I’m good with adding the logic.

I don’t think paper 1.16 is out yet. It appears to be trying to fetch from https://papermc.io/api/v1/paper/1.16/<VERSION>/download regardless of version, even though the latest is https://papermc.io/api/v1/paper/1.15.2/370/download. I just put in a ticket with the same issue.

Edit: for now, you can work around it by adding ‘-e VERSION=1.15.2 -e PAPERBUILD=370’. Likely the scripts are all switching to 1.16 because vanilla did, and the 3rd party stuff hasn’t caught up yet. You’ll need a legacy Minecraft client to connect, but that seems to be the situation unless you want to run vanilla.

@peace-blaster You can just set the VERSION=1.15.2 env variable until it’s fixed. (or until paper has a 1.16 build)

Latest image now improves the logic to fallback to latest available PaperMC version when VERSION=LATEST is used.

FYI PaperMC 1.16.2 is now available; however, I’m still working on enhancing the “pick latest PaperMC version” logic for the next case like this.

Well like you said before, we need a way to cap paper/spigot/etc at a specific version until they update. Edit: can probably also just pull down their git repos at docker build time and see what version they’re on