context: I’ve had a power outage, causing some hardware damage & my technical debt has caught up with me. Re-architecting/rebuilding my stack.
I’m looking for a straingt-up basic/standard method of standing up a Supervisor/Supervised instance INSIDE a Docker container instance, and NOT on the dom0 host.
What I’m trying to achieve is a sort of distributed architecture.
- I have a segregated network zone for all IoT - piping though a OpenWRT proxy/gateway - so that have visibility & control over what’s transiting my network
- A basic HA instance on a RPi on the IoT network to talk ‘locally’ to nodes
- The above HA instance is controlled or act as a worker-relay to the primary Supervisor on my LAN/lab - presently running in a VM
What I’m hoping to do is something along the lines of:
- Kill off my VM stack (HA is the only stack I still have running in a dedicated VM), as I don’t need the resource overhead
- Roll Docker (ala Portainer) on my server & a NUC
- HA/Super runs primarily on a dedicated NUC (in Docker swarm container), but with fail-over redundancy on server
- said HA is managed by by Docker swarm setup
- The other HA (non-super) on a RPi in my IoT-zone has a similar redundancy on my container server
I appreciate that HA/Super already runs on a Docker setup, so this should be able to run nested.
I do not want HA/Super to run on my server/dom0, but be managed (as a host) by my setup.
How can this be achieved?
Is there a docker-compose.yml available somewhere to spin up a Super instance?
Help would be appreciated