Minecraft Bedrock Server on Docker

Installing and Using OpenWrt Network and Wireless Configuration
1

Hi All, first of all I'm running FriendlyWRT as I think we haven't an official OpenWRT for the Nanopi R6S

I understand that is not the same thing and things may be different, crystal clear!

However the problem I'm facing I think is not too complicated, I'm just not an expert and I have to be missing something

I'm just playing with the Nanopi, prior to modifiying anything on my home network, my end goal is to put everything behind the Nanopi, for now this is not the case as I want to play with it and get familiar, my best case scenario is to install OpenWRT on it

Having say that this is how I have it connected on my network:

  ISP router 
  |--- All home devices (printer, cellulars, IoT, all of it)
  |--- Nanopi R6S
       |--- A mac mini to play with the nanopi

So all my home devices see the Nanopi using the WAN port and the IP 192.168.100.254

My mac mini use the Nanopi as the internet gateway using the IP 10.0.0.1

I have installed docker and I'm running a pi-hole so all DNS request from the private network 10.0.0.0/255.255.255.0 are being filtered by the pi-hole

I can reach the pi-hole web interface using the mac mini because I have set the web port to 8080 (this will be important later)

I have also configured as a docker container a minecraft-bedrock server as I normally do on any PC so I can play with the kids, I'm using the default port 19132

The issue I'm facing is that I cannot access it from WAN via 192.168.100.254, I can connect to it from the 10.0.0.1

I have tried adding very permissive firewall rules just to test, like accept all on WAN or LAN but that's is not helping, also custom like accepting connection from WAN to the 19132 port

However I noticed that the pi-hole web interface that runs also as a docker container does not have that problem when I share the web interface on the 8080 port, but if I change it to something else I cannot access it from the mac mini.

I can share any additional info and I appreciate any help

Cheers,

2

This is probably a Docker config problem.

Just a wild guess but perhaps you could try removing the /UDP from the port config. May not work but worth a shot.

3

Hi, I jus tried it with no luck, mi current /etc/init.d/minecraft-bedrock contains:

#!/bin/sh /etc/rc.common

START=99

start() {
        docker run \
                --name=holy-village \
                -d \
                -it \
                --restart=always \
                -e EULA=TRUE \
                -e LEVEL_SEED=4325227337 \
                -e GAMEMODE=survival \
                -e SERVER_NAME=HolyVillage \
                -e OPS=2533274986447779 \
                -p 19132:19132 \
                -p 19133:19133 \
                -v mc-bedrock-data:/data \
                itzg/minecraft-bedrock-server
}

stop() {
        docker stop holy-village
        docker rm holy-village
}

status() {
        if [ "$( docker container inspect -f '{{.State.Running}}' minecraft-bedrock-server )" = "true" ]
        then
                echo running
        else
                echo stopped
        fi
}

Cheers

4

I've been using docker-compose to manage/autostart my docker containers on OpenWrt and from my experience it works quite well.

5

Mine works too in that regard, the issue I have basically is to share the 19132 port over WAN xD

6

I don't think solution to that lies in a custom init script.