Magic Mirror on Rancher

[Wmsmckay]

I’m not sure where to post this so I hope I can find some help here.

I’ve been running my magic mirror on a raspberry pi for a few months plugged into a Roku smart tv. I would like to repurpose the pi for other projects but I’m very attached to my magic mirror dashboard. My solution right now is to run the magic mirror on my home server and access it over a browser from my roku TV. This would allow the pi to be reused and the tv would be able to just display the page without anything else plugged into it.

I’ve seen one issue is that Roku doesn’t have a web browser but I have found a few work arounds that I will try.

My server has Kubernetes running on it to manage all of my docker containers and I manage that with Rancher. I have been using this docker image and setup to create the container, which works. The problem is that when I go to the port that I publish it on (8075) I get an “unable to connect” error.

I have tried changing the address in the config file from 0.0.0.0 to my server’s ip to see if that would help but I just get a crash error from the container.

Any help with this issue would be much appreciated. Thanks in advance.

[sdetweil]

@wmsmckay connecting from where?

can u show a diagram

[Wmsmckay]

@sdetweil

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

Are you just wanting a network diagram?

[sdetweil]

@wmsmckay so u have a docker container, app running on address:“0.0.0.0”, port??? exposed on the server as port?? and the firewall on the server allows access for outside the server.

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

[Wmsmckay]

@sdetweil I have a VM running Rancher, Kubernetes and Docker at 10.0.0.16. I deployed a service running the Magic Mirror image from that on port 8075. When I navigate to 10.0.0.16:8075 I get nothing.

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

[sdetweil]

@wmsmckay the container cannot use it’s host address directly

[sdetweil]

@wmsmckay so mm config inside the container says port 8080, address:“0.0.0.0”, ipWhitelist:[]

and u map that to 8075 on the host

[Wmsmckay]

@sdetweil Corrent. I used the docker image above which maps port 80 in the container to an external port on the host which I set to 8075.

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

[sdetweil]

@wmsmckay no, inside the container it’s port 80

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

[Wmsmckay]

@sdetweil Right. I have that port mapped but when I navigate to host:8075, I just get an error.

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.