Error: Invalid or corrupt jarfile purpur-1.18-null.jar #1148
Description
Describe the problem
I'm aware that purpur has not currently published a 1.18 build. However, the container endlessly tries to download/verify a jar that does not exist.
❯ cat purpur-1.18-null.jar
{"error":{"code":404,"message":"Could not locate build"}}
Of course, a quick fix is to specifiy the version as 1.17, but is it possible to automatically fallback to the 1.17 version, considering the request returned a 404 status?
Container definition
docker run --rm --name=minecraft-server --log-driver=journald -e ENABLE_ROLLING_LOGS=true -e EULA=true -e MEMORY=4G -e "MOTD=\\u00A7b \\u00A7lplay.joel.tokyo\\u00A7r\\n\\u00A7c [1.17.1]" -e OVERRIDE_SERVER_PROPERTIES=true -e TYPE=purpur -p 25565:25565 -v /home/joel/minecraft-server:/data --tty itzg/minecraft-server
(managed with nixos virtualisation.oci-containers.containers)
Container logs
[init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 8 1000 100 4096 Dec 2 09:36 /data'
[init] Resolved version given LATEST into 1.18
[init] Resolving type given purpur
[init] Disabling whitelist
[init] Setting whitelist to 'false' in /data/server.properties
[init] Setting white-list to 'false' in /data/server.properties
[init] Setting enable-rcon to 'true' in /data/server.properties
[init] Setting rcon.password to 'minecraft' in /data/server.properties
[init] Setting rcon.port to '25575' in /data/server.properties
[init] Setting motd to '\u00A7b \u00A7lplay.joel.tokyo\u00A7r\n\u00A7c [1.17.1]' in /data/server.properties
[init] log4j2.xml already created, skipping
[init] Checking for JSON files.
[init] Setting initial memory to 4G and max to 4G
[init] Starting the Minecraft server...
Error: Invalid or corrupt jarfile purpur-1.18-null.jar
2021-12-02T09:36:51.452Z WARN mc-server-runner sub-process failed {"exitCode": 1}
2021-12-02T09:36:51.452Z INFO mc-server-runner Done```