Geoff Bourne

That's a fantastic video and explanation of macvlan @TheTinkerDad . I would like to add a "Tutorials" section to the README and link to your video, if that would be...

At container creation time the host port mapping should be adjusted to avoid host level conflicts. The container side port, the one in the EXPOSE, is within the container where...

Good to close the issue and PR?

That is not hardcoding the host port, just advertising the container port. https://docs.docker.com/engine/reference/builder/#expose How are you doing your port mapping? You can put whatever you want there and the `EXPOSE`d...

> Based on some testing it looks like this server is always listening on port 19132 I wouldn't expect that. Can you provide output/screenshots of that finding?

That is not influenced by the `EXPOSE` and is beyond my control. Have you built the image with your change to test?

Thank you for the research @bb-Ricardo , but I'm not sure if that indicates this is an image problem or a bedrock problem. I'm still assuming the latter since I...

A new container with that version started up fine for me and memory usage was stable: ``` > docker run -it --rm -e EULA=TRUE -p 19132:19132/udp itzg/minecraft-bedrock-server DEBU[0000] Using /data...

It looks like it has started and is waiting for connections.

Why do you need to access it? There are env var mappings for most (or all) of the properties https://github.com/itzg/docker-minecraft-bedrock-server/tree/master#server-properties