3 ms·
I also wish there was an option for people wanting to have a bit more control or fit it more tidily into an existing home stack. I hacked my own container image
by jhugo 5y ago
I also wish there was an option for people wanting to have a bit more control or fit it more tidily into an existing home stack. I hacked my own container image so that I could run it in my home k8s, but it wasn't easy — there are lots of undocumented dependencies, and there's no clear separation of state and config. It has by far the untidiest architecture of all the software I run on my home servers. Once it's up and running, though, HA is an amazing bit of software.
- eptcyka 5y agoI run it the forbidden way, via NixOS, and I do have to run the cycle of adding an integration, checking logs and then declaring which dependencies it needs and trying again. But once it works, it just works.
- onedr0p 5y agoWhat did you need to do to the Docker image to make it run in k8s? I'm using the stock image on k8s just fine.
- jhugo 5y agoThe stock image does all sorts of horrible things like modifying its own configuration at runtime and installing a variety of Python packages into attached volumes. So yes, you can "run" the stock image on k8s, if you abandon most of the advantages of deploying a container in the first place, but if you want to deploy it the way you would normally deploy a container, with the dependencies packaged into the image before it launches and tidily separated config & state, and have it behave predictably in future rather than just like a miniature pet server that needs care & attention, you have a little work to do.