Geoff Bourne

There's a wildcard/catch-all at the end that leaves VERSION as given https://github.com/itzg/docker-minecraft-bedrock-server/blob/c82dc81222bbf320b54a85cf794f3624912592d3/bedrock-entry.sh#L81

Since it mentions a UDP failure to port 53, there seems to be a DNS issue in or nearby your network. It could even be the docker daemon 's DNS...

It looks looks it's the upstream library since that response is retrieved here https://github.com/itzg/rcon-cli/blob/7f7f4f17150018dc375b3a1053f1b9d99c6eb178/cli/entry.go#L75

Good find; however, I'm not sure how to proceed given that unit test. It asserts it read the response sizes it expected, but in our case how would we know...

This is a popular problem :) Check out https://github.com/itzg/docker-minecraft-bedrock-server/issues/52, which points to https://github.com/itzg/docker-minecraft-bedrock-server/issues/28, for some ideas.

Oops, apparently I clicked the close button instead of just commenting. Ah yes, you found what I was going explain about the container's baked in declaration of 19132. That particular...

> Can you share your understanding of what the EXPOSE command does? If I'm reading the [docs](https://docs.docker.com/engine/reference/builder/#expose) correctly, it seems like it should have no effect unless you use "docker...

@illiteratealliterator I haven't tested it out, but reading through your code, etc everything looks great. In your example compose file though, I'm curious why you needed to set `SERVER_PORT` different...

Oh, your `manymine` doesn't fully proxy the client connections, just the discovery/broadcast ping? That now makes sense why the port exposing and `SERVER_PORT` setting.

Rather than `docker run`ing them, it's use to use compose, such as https://raw.githubusercontent.com/itzg/docker-rcon-web-admin/master/docker-compose.yml however, a quick solution if you just want to run commands is exec'ing into the minecraft container...