docker-minecraft-server: failed to download spigot
Hi
I am using the spigot server. My container wont go up after updating. Is there anything I’m doing wrong? I would be so grateful for your help
Here is my docker-compose.yml
minecraft-server:
ports:
- "25565:25565"
environment:
EULA: "TRUE"
MEMORY: 8G
TYPE: SPIGOT
VERSION: latest
MAX_PLAYERS: 100
DIFFICULTY: normal
ENABLE_AUTOPAUSE: "TRUE"
image: itzg/minecraft-server
container_name: mc
tty: true
stdin_open: true
restart: always
volumes:
- ./data:/data
Here are my docker-compose logs
mc | [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 8 1000 1000 4096 Oct 29 17:24 /data'
mc | [init] Resolved version given latest into 1.16.3
mc | [init] Autopause functionality enabled
mc | [init] Resolving type given SPIGOT
mc | [init] Downloading Spigot from https://cdn.getbukkit.org/spigot/spigot-1.16.3.jar ...
mc |
mc | ERROR: failed to download from https://cdn.getbukkit.org/spigot/spigot-1.16.3.jar
mc | Visit https://getbukkit.org/download/spigot to lookup the
mc | exact version, such as 1.4.6-R0.4-SNAPSHOT or 1.8-R0.1-SNAPSHOT-LATEST
mc |
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 31 (13 by maintainers)
Commits related to this issue
- Added debug output for bukkit/sigot type For #655 — committed to itzg/docker-minecraft-server by itzg 4 years ago
- Improved handling of bad spigot/bukkit downloads via temp file For #655 — committed to itzg/docker-minecraft-server by itzg 4 years ago
- Revert "Improved handling of bad spigot/bukkit downloads via temp file For #655" This reverts commit e56a74dc — committed to itzg/docker-minecraft-server by itzg 4 years ago
- Added debug logging of bukkit/spigot curl download For #655 — committed to itzg/docker-minecraft-server by itzg 4 years ago
- Removed invalid spigot/bukkit download along with debug of content For #655 — committed to itzg/docker-minecraft-server by itzg 4 years ago
Latest image now cleans up a bad download.
Thanks @MichaelLeeHobbs , yeah it feels like something external is failing and am hoping the verbose curl logging will help a little more to debug.
As for the side note, there’s one example here https://github.com/itzg/docker-bungeecord/tree/master/docs
As a quick fix I’ll probably revert that commit since I’m not sure either why the grep is failing in some of these cases…but not when I tested it.
Please pull the latest image and try with that. I tweaked the download logic to download to a temp file and check the validity of that. I’m hoping that avoid some or all cases where the “not publicly accessible” type HTML content doesn’t clobber the real jar file.