docker-minecraft-bedrock-server icon indicating copy to clipboard operation
docker-minecraft-bedrock-server copied to clipboard

Error "failed to download" when using Latest

Open Eric-Burdo opened this issue 3 years ago • 4 comments

I have the docker setup on my Synology.

If I tell it to download 1.16 or 1.17 - the servers starts and runs fine. It will download and execute.

When I tell it to use 1.18 or latest, I get an error.

  • Downloading Bedrock server version 1.18.12.01 ...
  • curl: (23) Failure writing output to destination
  • ERROR failed to download from https://minecraft.azureedge.net/bin-linux/bedrock-server-1.18.12.01.zip
  • Double check that the given VERSION is valid

I saw in a comment on this site that someone else is getting the same error: https://drfrankenstein.co.uk/2022/02/23/minecraft-bedrock-console-edition-server-in-docker-on-a-synology-nas/

Unfortunately, the Bedrock launcher doesn't let me choose versions, so I can't play on my own server atm.

I've attached an HTML file (please rename it) that is a Export of the log from my Synology server... It has a valid 1.17 launch, and then a couple of failures for latest/1.18

mcbedrock.html.txt

Eric-Burdo avatar Mar 05 '22 21:03 Eric-Burdo

Forgot to mention... if I copy/paste that bedrock-server-1.18 ZIP link into my browser, it properly downloads the file.

Eric-Burdo avatar Mar 05 '22 21:03 Eric-Burdo

It sounds like the download itself is fine. Something is not correct with the filesystem/volume you have attached to the container's data path since it reports

Failure writing output to destination

itzg avatar Mar 06 '22 01:03 itzg

But why would 1.16 and 1.17 all work perfectly fine, but 1.8 (or latest) fails? If it was a filesystem issue, wouldn't that affect any version?

And the 404 error from the download... only happens on 1.18 (or latest). That's a download issue of some sort.

Eric-Burdo avatar Mar 06 '22 19:03 Eric-Burdo

But why would 1.16 and 1.17 all work perfectly fine, but 1.8 (or latest) fails? If it was a filesystem issue, wouldn't that affect any version?

I'm not sure. That's something to investigate on your system.

And the 404 error from the download... only happens on 1.18 (or latest). That's a download issue of some sort.

I don't see a 404.

Worked fine for me:

> docker run -it --rm -e EULA=TRUE itzg/minecraft-bedrock-server
DEBU[0000] Using /data to match uid and gid
DEBU[0000] Resolved UID=0 from match path
DEBU[0000] Resolved GID=0 from match path
Looking up latest version...
Downloading Bedrock server version 1.18.12.01 ...
Starting Bedrock server...
NO LOG FILE! - setting up server logging...
[2022-03-06 20:32:40:135 INFO] Starting Server
[2022-03-06 20:32:40:135 INFO] Version 1.18.12.01
[2022-03-06 20:32:40:135 INFO] Session ID 65fd47d0-0e36-4e4f-8b3b-70fee9952c3c
[2022-03-06 20:32:40:136 INFO] Level Name: Bedrock level
[2022-03-06 20:32:40:139 INFO] Game mode: 0 Survival
[2022-03-06 20:32:40:139 INFO] Difficulty: 1 EASY
[2022-03-06 20:32:40:229 INFO] opening worlds/Bedrock level/db
[2022-03-06 20:32:41:302 INFO] IPv4 supported, port: 19132
[2022-03-06 20:32:41:302 INFO] IPv6 not supported
[2022-03-06 20:32:42:746 INFO] Server started.
[2022-03-06 20:32:42:764 INFO] IPv4 supported, port: 33259
[2022-03-06 20:32:42:764 INFO] IPv6 not supported

itzg avatar Mar 06 '22 20:03 itzg