@sdetweil Not normally no, but for some things you can grant a hole in the container to allow direct access to some things. For example I run Jenkins in a Docker container but grant access to the docker socket so that Jenkins can actually launch build steps in containers. I think that it is possible to run GPU jobs in containers. But I agree with you that none of this is the norm.

I’ll take a look at pm2.

@sdetweil One thing I’d love to do is to run the browser from a container pinned to that specific node so that if it did die it could be killed/restarted using normal kubernetes container management. But running a GUI program from a container seems to be underexplored territory.

The other approach I can think of would require being able to remotely kill/restart the browser on the console from an ssh connection. Currently I use a ~/.config/wayfire.ini file (created via an Ansible role) to launch chromium on boot, but that doesn’t make it any easier to relaunch after a browser crash.

I’ve got the magicmirror software built as a container and deployed to a kubernetes (k3s) cluster. For the front end I’ve got a Raspberry Pi 4 with 4G RAM running Bullseye and Chromium automatically on boot and this same pi is also one of the nodes in the k3s cluster so it’s often the case that the magic mirror server is running on the same machine as the browser showing it.

Occasionally the mirror freezes and stops updating but even while this is the case I can still connect to the mm server from another computer so the server is fine, the issue seems to be client side. Before I switched to the k3s deployment if the mirror froze I’d tell family members it was ok to just unplug/replug the pi but now that other things could be affected I’d rather not do that.

I’m not sure if the Chromium browser is actually crashing or if it is possible that once a periodic update fails for whatever reason that mm doesn’t get updates after that.

So has anyone implemented some kind of watchdog that will restart the browser in such a situation or some kind of plugin for mm that forces a major refresh every once in a while just in case things froze?

I’m familiar with git, but not github as much. Since I forked your repository to make my change, then did a pull request which you accepted, I now show my repo as being one commit behind yours. How do I tell github to pull that commit, or do I just delete my repo and fork again when/if needed?

I created a pull request that I’d like merged. I added a config parameter that allows you to specify the type of map to display, my favorite is the hybrid which shows a satellite image with the roads on top. I left the default to display just the road maps as before.

I’ve been looking for a simple way to build a dashboard for the home automation system I wrote, even if worst case it’s just a good example of node.js programming to start from. I previously looked at NODE-RED, but found that it had some limitations that rule it out.

One big requirement for me is to be able to display images - for example if a motion detector outside trips I get a MQTT notification on a topic and I’d like to be able to display a picture on the mirror taken from the camera in that area. The image could be the entire background of the display, or it could be in a window.

Is anyone aware of any examples where someone has used MM in a home monitoring type situation? I would assume this sort of thing has been done before.