Having trouble starting a vanilla server #2208

grantjbutler · 2023-06-13T01:48:48Z

grantjbutler
Jun 13, 2023
Sponsor

Hi there! I'm trying to start a vanilla server, but am running into some issues. After running docker-compose up -d, starting the server gets stuck on the Finding version manifest for 1.19.2 step. Eventually, I get a ConnectTimeoutException. I've pasted the whole DEBUG log below, as well as the docker-compose.yml for this server. I am able to fetch version manifest file with curl on the machine where I'm trying to run the server, so I don't know if that means that I messed something up with the configuration of the server or if there's something else going on here that I'm not aware of.

version: "3"

services:
        minecraft:
                image: itzg/minecraft-server
                ports:
                        - "25565:25565"
                volumes:
                        - "/home/legosjedi/minecraft/vanilla/data:/data:rw"
                environment:
                        EULA: "true"
                        DIFFICULTY: hard
                        MEMORY: "4G"
                        VERSION: "1.19.2"
                        DEBUG: true
                container_name: "vanilla-minecraft"
                tty: true
                stdin_open: true
                restart: always

+ export HOME=/data
+ HOME=/data
++ id -u
++ id -g
++ ls -lnd /data
+ log 'Running as uid=1000 gid=1000 with /data as '\''drwxrwxr-x 2 1000 1000 4096 Jun 13 01:42 /data'\'''
+ local oldState
++ shopt -po xtrace
+ oldState='set -o xtrace'
+ shopt -u -o xtrace
[init] 2023-06-13 01:43:06+00:00 Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 2 1000 1000 4096 Jun 13 01:42 /data'
+ '[' '!' -e /data/eula.txt ']'
+ isTrue false
+ case "${1,,}" in
+ return 1
+ isTrue false
+ case "${1,,}" in
+ return 1
+ [[ -n '' ]]
+ [[ -n '' ]]
+ echo password=3c6f053329c16e171528741e
+ fixJavaPath
+ which java
+ cd /data
+ export ORIGINAL_TYPE=VANILLA
+ ORIGINAL_TYPE=VANILLA
+ isTrue false
+ case "${1,,}" in
+ return 1
+ isTrue false
+ case "${1,,}" in
+ return 1
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ :
+ case "${TYPE^^}" in
+ [[ -n '' ]]
+ resolveVersion
+ VERSIONS_JSON=https://launchermeta.mojang.com/mc/game/version_manifest.json
+ case "X$VERSION" in
+ VANILLA_VERSION=1.19.2
+ export VANILLA_VERSION
++ get_major_version 1.19.2
++ version=1.19.2
++ echo 1.19.2
++ cut -d. -f 1-2
+ MAJOR_VANILLA_VERSION=1.19
+ export MAJOR_VANILLA_VERSION
+ log 'Resolved version given 1.19.2 into 1.19.2 and major version 1.19'
+ local oldState
++ shopt -po xtrace
+ oldState='set -o xtrace'
+ shopt -u -o xtrace
[init] 2023-06-13 01:43:06+00:00 Resolved version given 1.19.2 into 1.19.2 and major version 1.19
+ log 'Resolving type given VANILLA'
+ local oldState
++ shopt -po xtrace
+ oldState='set -o xtrace'
+ shopt -u -o xtrace
[init] 2023-06-13 01:43:06+00:00 Resolving type given VANILLA
+ case "${TYPE^^}" in
+ exec /start-deployVanilla
+ set -o pipefail
+ export SERVER=minecraft_server.1.19.2.jar
+ SERVER=minecraft_server.1.19.2.jar
+ '[' '!' -e minecraft_server.1.19.2.jar ']'
+ debug 'Finding version manifest for 1.19.2'
+ isDebugging
+ isTrue true
+ case "${1,,}" in
+ return 0
+ return 0
+ log 'DEBUG: Finding version manifest for 1.19.2'
+ local oldState
++ shopt -po xtrace
+ oldState='set -o xtrace'
+ shopt -u -o xtrace
[init] 2023-06-13 01:43:06+00:00 DEBUG: Finding version manifest for 1.19.2
++ get https://launchermeta.mojang.com/mc/game/version_manifest.json
++ mc-image-helper get https://launchermeta.mojang.com/mc/game/version_manifest.json
++ jq --arg VANILLA_VERSION 1.19.2 --raw-output '[.versions[]|select(.id == $VANILLA_VERSION)][0].url'
[mc-image-helper] 01:43:06.926 DEBUG : Getting uri=https://launchermeta.mojang.com/mc/game/version_manifest.json
[mc-image-helper] 01:43:06.929 DEBUG : Executing GET /mc/game/version_manifest.json with headers=[]
[mc-image-helper] 01:43:06.933 DEBUG : Intercepting request uri=https://launchermeta.mojang.com/mc/game/version_manifest.json
[mc-image-helper] 01:47:27.601 ERROR : 'get' command failed. Version is 1.29.2
org.apache.hc.client5.http.ConnectTimeoutException: Connect to https://launchermeta.mojang.com:443 [launchermeta.mojang.com/13.107.246.51, launchermeta.mojang.com/13.107.213.51] failed: Connection timed out
	at org.apache.hc.client5.http.ConnectExceptionSupport.createConnectTimeoutException(ConnectExceptionSupport.java:52)
	at org.apache.hc.client5.http.ConnectExceptionSupport.enhance(ConnectExceptionSupport.java:74)
	at org.apache.hc.client5.http.impl.io.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:195)
	at org.apache.hc.client5.http.impl.io.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:447)
	at org.apache.hc.client5.http.impl.classic.InternalExecRuntime.connectEndpoint(InternalExecRuntime.java:162)
	at org.apache.hc.client5.http.impl.classic.InternalExecRuntime.connectEndpoint(InternalExecRuntime.java:172)
	at org.apache.hc.client5.http.impl.classic.ConnectExec.execute(ConnectExec.java:142)
	at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
	at org.apache.hc.client5.http.impl.classic.ProtocolExec.execute(ProtocolExec.java:192)
	at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
	at org.apache.hc.client5.http.impl.classic.HttpRequestRetryExec.execute(HttpRequestRetryExec.java:96)
	at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
	at org.apache.hc.client5.http.impl.classic.ContentCompressionExec.execute(ContentCompressionExec.java:152)
	at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
	at org.apache.hc.client5.http.impl.classic.RedirectExec.execute(RedirectExec.java:115)
	at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
	at me.itzg.helpers.http.LatchingUrisInterceptor.execute(LatchingUrisInterceptor.java:27)
	at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
	at org.apache.hc.client5.http.impl.classic.InternalHttpClient.doExecute(InternalHttpClient.java:170)
	at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:245)
	at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:188)
	at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:162)
	at me.itzg.helpers.get.GetCommand.processSingleUri(GetCommand.java:440)
	at me.itzg.helpers.get.GetCommand.call(GetCommand.java:196)
	at me.itzg.helpers.get.GetCommand.call(GetCommand.java:55)
	at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
	at picocli.CommandLine.access$1500(CommandLine.java:148)
	at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
	at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
	at picocli.CommandLine.execute(CommandLine.java:2170)
	at me.itzg.helpers.McImageHelper.main(McImageHelper.java:143)
Caused by: java.net.ConnectException: Connection timed out
	at java.base/sun.nio.ch.Net.pollConnect(Native Method)
	at java.base/sun.nio.ch.Net.pollConnectNow(Unknown Source)
	at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(Unknown Source)
	at java.base/sun.nio.ch.NioSocketImpl.connect(Unknown Source)
	at java.base/java.net.SocksSocketImpl.connect(Unknown Source)
	at java.base/java.net.Socket.connect(Unknown Source)
	at org.apache.hc.client5.http.ssl.SSLConnectionSocketFactory.lambda$connectSocket$0(SSLConnectionSocketFactory.java:232)
	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
	at org.apache.hc.client5.http.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:231)
	at org.apache.hc.client5.http.impl.io.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:181)
	... 31 common frames omitted
+ versionManifestUrl=
+ result=1
+ '[' 1 '!=' 0 ']'
+ log 'ERROR: failed to obtain version manifest URL (1)'
+ local oldState
++ shopt -po xtrace
+ oldState='set -o xtrace'
+ shopt -u -o xtrace
[init] 2023-06-13 01:47:27+00:00 ERROR: failed to obtain version manifest URL (1)
+ exit 1

itzg · 2023-06-13T02:49:25Z

itzg
Jun 13, 2023
Maintainer

Seems to be a networking issue and probably temporary since the root error is

ERROR : 'get' command failed. Version is 1.29.2
org.apache.hc.client5.http.ConnectTimeoutException: Connect to https://launchermeta.mojang.com:443 [launchermeta.mojang.com/13.107.246.51, launchermeta.mojang.com/13.107.213.51] failed: Connection timed out

5 replies

grantjbutler Jun 13, 2023
Author Sponsor

I would agree with you, but I can do a curl just fine from the computer I'm using to host the server:

$ curl -I https://launchermeta.mojang.com/mc/game/version_manifest.json
HTTP/2 200
cache-control: public, max-age=120
content-length: 158496
content-type: application/json
content-md5: tBcYEqYIQ3IX5hlhk553Aw==
last-modified: Mon, 12 Jun 2023 14:13:41 GMT
etag: 0x8DB6B4F39CC01AB
x-cache: TCP_HIT
x-ms-request-id: e711848d-e01e-0044-78ad-9d7f8a000000
x-ms-version: 2009-09-19
x-ms-lease-status: unlocked
x-ms-blob-type: BlockBlob
x-azure-ref-originshield: 0w+2HZAAAAABC7NQfpmW4SokFqnxW3HQmRE0yQUExMDkxMjA4MDE3ADJhYmYyZTY2LWJkZWEtNDVjYy05YTAzLTY0YTNiZmM0NzIzZg==
access-control-allow-origin: *
x-azure-ref: 0Oe6HZAAAAAC5wnokt093S7k1fcHSfU6tQ0gxQUEyMDIwNjA5MDIxADJhYmYyZTY2LWJkZWEtNDVjYy05YTAzLTY0YTNiZmM0NzIzZg==
date: Tue, 13 Jun 2023 04:19:05 GMT

Additionally, if I just run an even more basic server, it will get past the fetching of the manifest file and will download 1.20.1 (I shorted this to just enough to show that it gets past the point that it does for 1.16.5):

$ docker run -e EULA=TRUE -e DEBUG=true itzg/minecraft-server
+ export HOME=/data
+ HOME=/data
++ id -u
++ id -g
++ ls -lnd /data
+ log 'Running as uid=1000 gid=1000 with /data as '\''drwxrwxr-x 2 1000 1000 4096 Jun 12 19:40 /data'\'''
+ local oldState
++ shopt -po xtrace
+ oldState='set -o xtrace'
+ shopt -u -o xtrace
[init] 2023-06-13 04:25:12+00:00 Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 2 1000 1000 4096 Jun 12 19:40 /data'
+ '[' '!' -e /data/eula.txt ']'
+ isTrue TRUE
+ case "${1,,}" in
+ return 0
+ writeEula
++ date
+ echo '# Generated via Docker
# Tue 13 Jun 2023 04:25:12 AM UTC
eula=true
'
+ isTrue false
+ case "${1,,}" in
+ return 1
+ isTrue false
+ case "${1,,}" in
+ return 1
+ [[ -n '' ]]
+ [[ -n '' ]]
+ echo password=bf76d1a33450925ec8616ab1
+ fixJavaPath
+ which java
+ cd /data
+ export ORIGINAL_TYPE=VANILLA
+ ORIGINAL_TYPE=VANILLA
+ isTrue false
+ case "${1,,}" in
+ return 1
+ isTrue false
+ case "${1,,}" in
+ return 1
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ :
+ case "${TYPE^^}" in
+ [[ -n '' ]]
+ resolveVersion
+ VERSIONS_JSON=https://launchermeta.mojang.com/mc/game/version_manifest.json
+ case "X$VERSION" in
++ get --json-path '$.latest.release' https://launchermeta.mojang.com/mc/game/version_manifest.json
++ mc-image-helper get --json-path '$.latest.release' https://launchermeta.mojang.com/mc/game/version_manifest.json
[mc-image-helper] 04:25:13.297 DEBUG : Getting uri=https://launchermeta.mojang.com/mc/game/version_manifest.json
[mc-image-helper] 04:25:13.300 DEBUG : Executing GET /mc/game/version_manifest.json with headers=[Accept: application/json]
[mc-image-helper] 04:25:13.304 DEBUG : Intercepting request uri=https://launchermeta.mojang.com/mc/game/version_manifest.json
[mc-image-helper] 04:25:13.546 DEBUG : Post-request capturing redirectLocations=[]
[mc-image-helper] 04:25:13.546 DEBUG : Response: status=200, reason=OK, headers=[Cache-Control: public, max-age=120, Transfer-Encoding: chunked, Content-Type: application/json, Last-Modified: Mon, 12 Jun 2023 14:13:41 GMT, ETag: 0x8DB6B4F39CC01AB, X-Cache: TCP_HIT, x-ms-request-id: 4c275a2e-401e-0062-65ae-9d14b5000000, x-ms-version: 2009-09-19, x-ms-lease-status: unlocked, x-ms-blob-type: BlockBlob, X-Azure-Ref-OriginShield: 0UO+HZAAAAACuptuShJfbS7OKYTKVUXd1RE0yQUExMDkxMjA4MDIxADJhYmYyZTY2LWJkZWEtNDVjYy05YTAzLTY0YTNiZmM0NzIzZg==, Access-Control-Allow-Origin: *, X-Azure-Ref: 0qe+HZAAAAAD88s+XYYNsQYY0UkFEuwOuQ0gxQUEyMDIwNjA4MDM3ADJhYmYyZTY2LWJkZWEtNDVjYy05YTAzLTY0YTNiZmM0NzIzZg==, Date: Tue, 13 Jun 2023 04:25:12 GMT]
+ VANILLA_VERSION=1.20.1
+ export VANILLA_VERSION
++ get_major_version 1.20.1
++ version=1.20.1
++ echo 1.20.1
++ cut -d. -f 1-2
+ MAJOR_VANILLA_VERSION=1.20
+ export MAJOR_VANILLA_VERSION
+ log 'Resolved version given LATEST into 1.20.1 and major version 1.20'
+ local oldState
++ shopt -po xtrace
+ oldState='set -o xtrace'
+ shopt -u -o xtrace
[init] 2023-06-13 04:25:13+00:00 Resolved version given LATEST into 1.20.1 and major version 1.20
+ log 'Resolving type given VANILLA'
+ local oldState
++ shopt -po xtrace
+ oldState='set -o xtrace'
+ shopt -u -o xtrace
[init] 2023-06-13 04:25:13+00:00 Resolving type given VANILLA
+ case "${TYPE^^}" in
+ exec /start-deployVanilla
+ set -o pipefail
+ export SERVER=minecraft_server.1.20.1.jar
+ SERVER=minecraft_server.1.20.1.jar
+ '[' '!' -e minecraft_server.1.20.1.jar ']'
+ debug 'Finding version manifest for 1.20.1'
+ isDebugging
+ isTrue true
+ case "${1,,}" in
+ return 0
+ return 0
+ log 'DEBUG: Finding version manifest for 1.20.1'
+ local oldState
++ shopt -po xtrace
+ oldState='set -o xtrace'
+ shopt -u -o xtrace
[init] 2023-06-13 04:25:13+00:00 DEBUG: Finding version manifest for 1.20.1
++ get https://launchermeta.mojang.com/mc/game/version_manifest.json
++ mc-image-helper get https://launchermeta.mojang.com/mc/game/version_manifest.json
++ jq --arg VANILLA_VERSION 1.20.1 --raw-output '[.versions[]|select(.id == $VANILLA_VERSION)][0].url'
[mc-image-helper] 04:25:14.197 DEBUG : Getting uri=https://launchermeta.mojang.com/mc/game/version_manifest.json
[mc-image-helper] 04:25:14.200 DEBUG : Executing GET /mc/game/version_manifest.json with headers=[]
[mc-image-helper] 04:25:14.203 DEBUG : Intercepting request uri=https://launchermeta.mojang.com/mc/game/version_manifest.json
[mc-image-helper] 04:25:14.429 DEBUG : Post-request capturing redirectLocations=[]
[mc-image-helper] 04:25:14.430 DEBUG : Response: status=200, reason=OK, headers=[Cache-Control: public, max-age=120, Transfer-Encoding: chunked, Content-Type: application/json, Last-Modified: Mon, 12 Jun 2023 14:13:41 GMT, ETag: 0x8DB6B4F39CC01AB, X-Cache: TCP_HIT, x-ms-request-id: 4c275a2e-401e-0062-65ae-9d14b5000000, x-ms-version: 2009-09-19, x-ms-lease-status: unlocked, x-ms-blob-type: BlockBlob, X-Azure-Ref-OriginShield: 0UO+HZAAAAACuptuShJfbS7OKYTKVUXd1RE0yQUExMDkxMjA4MDIxADJhYmYyZTY2LWJkZWEtNDVjYy05YTAzLTY0YTNiZmM0NzIzZg==, Access-Control-Allow-Origin: *, X-Azure-Ref: 0qu+HZAAAAACdwiAchjPQTrNhbvPYtW4iQ0gxQUEyMDIwNjA5MDQ5ADJhYmYyZTY2LWJkZWEtNDVjYy05YTAzLTY0YTNiZmM0NzIzZg==, Date: Tue, 13 Jun 2023 04:25:13 GMT]
+ versionManifestUrl=https://piston-meta.mojang.com/v1/packages/715ccf3330885e75b205124f09f8712542cbe7e0/1.20.1.json
+ result=0
+ '[' 0 '!=' 0 ']'
+ '[' https://piston-meta.mojang.com/v1/packages/715ccf3330885e75b205124f09f8712542cbe7e0/1.20.1.json = null ']'
+ debug 'Found version manifest at https://piston-meta.mojang.com/v1/packages/715ccf3330885e75b205124f09f8712542cbe7e0/1.20.1.json'
+ isDebugging
+ isTrue true
+ case "${1,,}" in
+ return 0
+ return 0
+ log 'DEBUG: Found version manifest at https://piston-meta.mojang.com/v1/packages/715ccf3330885e75b205124f09f8712542cbe7e0/1.20.1.json'
+ local oldState
++ shopt -po xtrace
+ oldState='set -o xtrace'
+ shopt -u -o xtrace
[init] 2023-06-13 04:25:14+00:00 DEBUG: Found version manifest at https://piston-meta.mojang.com/v1/packages/715ccf3330885e75b205124f09f8712542cbe7e0/1.20.1.json
++ get --json-path '$.downloads.server.url' https://piston-meta.mojang.com/v1/packages/715ccf3330885e75b205124f09f8712542cbe7e0/1.20.1.json
++ mc-image-helper get --json-path '$.downloads.server.url' https://piston-meta.mojang.com/v1/packages/715ccf3330885e75b205124f09f8712542cbe7e0/1.20.1.json
^C[mc-image-helper] 04:25:15.077 DEBUG : Getting uri=https://piston-meta.mojang.com/v1/packages/715ccf3330885e75b205124f09f8712542cbe7e0/1.20.1.json
[mc-image-helper] 04:25:15.080 DEBUG : Executing GET /v1/packages/715ccf3330885e75b205124f09f8712542cbe7e0/1.20.1.json with headers=[Accept: application/json]
[mc-image-helper] 04:25:15.084 DEBUG : Intercepting request uri=https://piston-meta.mojang.com/v1/packages/715ccf3330885e75b205124f09f8712542cbe7e0/1.20.1.json
[mc-image-helper] 04:25:15.306 DEBUG : Post-request capturing redirectLocations=[]
[mc-image-helper] 04:25:15.306 DEBUG : Response: status=200, reason=OK, headers=[Cache-Control: public, max-age=1209600, Transfer-Encoding: chunked, Content-Type: application/json, Last-Modified: Mon, 12 Jun 2023 13:35:57 GMT, ETag: 0x8DB6B49F3D788B5, X-Cache: TCP_HIT, x-ms-request-id: ea79015c-001e-004a-5138-9ddd97000000, x-ms-version: 2009-09-19, x-ms-lease-status: unlocked, x-ms-blob-type: BlockBlob, X-Azure-Ref-OriginShield: 0bpGHZAAAAAAnT7qkC3xMQ6XqMP0E2YlYRE0yQUExMDkxMjA3MDExADJhYmYyZTY2LWJkZWEtNDVjYy05YTAzLTY0YTNiZmM0NzIzZg==, Access-Control-Allow-Origin: *, X-Azure-Ref: 0q++HZAAAAABwrJgtcLR0TI12RBg6LznJQ0gxQUEyMDIwNjA5MDMzADJhYmYyZTY2LWJkZWEtNDVjYy05YTAzLTY0YTNiZmM0NzIzZg==, Date: Tue, 13 Jun 2023 04:25:14 GMT]
+ serverDownloadUrl=https://piston-data.mojang.com/v1/objects/84194a2f286ef7c14ed7ce0090dba59902951553/server.jar
+ '[' https://piston-data.mojang.com/v1/objects/84194a2f286ef7c14ed7ce0090dba59902951553/server.jar = null ']'
+ log 'Downloading 1.20.1 server...'
+ local oldState
++ shopt -po xtrace
+ oldState='set -o xtrace'
+ shopt -u -o xtrace
[init] 2023-06-13 04:25:15+00:00 Downloading 1.20.1 server...

Is there anything else I can do with the container for my 1.16.5 server to try to get more details on why fetching the manifest file may fail there, but will succeed with this 1.20.1 server?

itzg Jun 13, 2023
Maintainer

It still seems like a temporary failure, as I mentioned. Also, showing connectivity from the host is a helpful data point but does not fully confirm/deny connectivity from within a container on your system.

So, if you again try 1.16.5 it fails?

The code goes through exact same logic, which you can verify yourself with the same debug output you just showed.

grantjbutler Jun 13, 2023
Author Sponsor

Also, showing connectivity from the host is a helpful data point but does not fully confirm/deny connectivity from within a container on your system.

Right, which is why I was wondering if there was a way to test networking from within the container itself (like if there was a way I could try to run that curl command from the container), to try to get more details on where the issue might be.

So, if you again try 1.16.5 it fails?

Yup, I tried again this morning, and the 1.16.5 server is still failing at the same step.

The code goes through exact same logic, which you can verify yourself with the same debug output you just showed.

Yeah, I'm probably just as confused as you are here as to why this is happening. To add further to the confusion, if I try to run the 1.16.5 server standalone, from the command line, without using docker compose, (docker run -e EULA=TRUE -e DEBUG=true -e VERSION=1.16.5 itzg/minecraft-server) then everything's fine. It'll get past that point and properly download the manifest file and move on to downloading the server. There's got to be something wrong with my docker-compose.yml, but I'm not 100% sure what right now. I'll play around with different combinations of things and report back on what I find.

itzg Jun 13, 2023
Maintainer

curl is installed into the image, so you can use

docker run --rm --entrypoint curl itzg/minecraft-server CURL_ARGS_HERE

or with compose file:

docker compose run --rm --entrypoint curl SERVICE CURL_ARGS_HERE

grantjbutler Jun 14, 2023
Author Sponsor

It looks like something might've been broken with my docker installation. I did an uninstall and reinstall and now I'm able to download servers from within containers that are created with a docker-compose.yml file. I don't know enough about docker internals to know what went wrong (maybe I was on an outdated version of docker and didn't realize it?), but it looks like things are back to normal for me. Sorry for the hassle!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Having trouble starting a vanilla server #2208

{{title}}

Replies: 1 comment 5 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

Having trouble starting a vanilla server #2208

grantjbutler Jun 13, 2023 Sponsor

Replies: 1 comment · 5 replies

itzg Jun 13, 2023 Maintainer

grantjbutler Jun 13, 2023 Author Sponsor

itzg Jun 13, 2023 Maintainer

grantjbutler Jun 13, 2023 Author Sponsor

itzg Jun 13, 2023 Maintainer

grantjbutler Jun 14, 2023 Author Sponsor

grantjbutler
Jun 13, 2023
Sponsor

Replies: 1 comment 5 replies

itzg
Jun 13, 2023
Maintainer

grantjbutler Jun 13, 2023
Author Sponsor

itzg Jun 13, 2023
Maintainer

grantjbutler Jun 13, 2023
Author Sponsor

itzg Jun 13, 2023
Maintainer

grantjbutler Jun 14, 2023
Author Sponsor