I have been using this docker image and setup to create the container, which works.

this docker image is not maintained anymore, meanwhile the image build fails so the image is old without containing security fixes. Also this image does not contain the latest mm version v2.16.0.

I deployed a service running the Magic Mirror image from that on port 8075.

can you show us this service? kubectl get service <service-name> -o yaml

I wrote a helm chart for running mm in k8s, you find it here.

then u can use browser on docker host to the container IP and the mm port.

that proves the container config is right for the mm config

then you can check the host port, localhost:8075, and the inspect will show u the port mapping definition. should show what is in the compose file

then u can go to another machine

In my logs it says

Ready to go! Please point your browser to: http://0.0.0.0:8075

But going to 10.0.0.16:8075 there is nothing there.

the mapping is done outside, nat translation
the app inside doesn’t know

app configured to port 80
docker does nat and exposes that on the docker host as 8075 (-p 8075:80)

this is exactly the same as if u wanted your mm on a pi, exposed to the internet
8080 on pi, router says map requests from 8075 on internet to port 8080 on the pi.

pi doesn’t know

The config file is set to the default which is

var config = {
  address: "0.0.0.0", // Address to listen on, can be:
  port: 8075,
  ipWhitelist: [], // Set [] to allow all IP addresses

and u map that to 8075 on the host

I have other service running on the stack that I can reach just fine e.g. pihole, mysql databases, a web server.

if u run a default http server container on that same server, can u access from the other system?

I’m connecting from a device on the same network that the server is running on.

Are you just wanting a network diagram?

can u show a diagram