What is your reason for running two separate Debian docker hosts with under 5 containers in total? That seems like quite the overhead? And why did you choose to install Nextcloud on your TrueNAS server?
Running multiple Proxmox hosts in a cluster makes sense so you can swap VMs from one the other and have extra hardware reliability. I’d also get grouping your containers on different Docker VMs the apply the same security rules to containers in a group (internally vs. externally available for example).
But how does a faulty Immich container take down a Plex container?
Something decides it’s going to fill your disk up with noise and plex enters a crash loop as it can’t write to disk any more.
Your reverse proxy decides it’s not going to issue valid SSL certificates so all your plex clients refuse to connect.
One day an OS update decides your network configuration wasn’t important, and your OS throws a shit fit because there’s no route to 192.168.1.100 any more
What is your reason for running two separate Debian docker hosts with under 5 containers in total? That seems like quite the overhead? And why did you choose to install Nextcloud on your TrueNAS server?
Not OP. But i do the same.
I have multiple proxmox hosts, running multiple VMs, each running containers.
I do it so I can minimise disruption. Fixing a fault in immich doesn’t mean the house is without plex for a week.
Running multiple Proxmox hosts in a cluster makes sense so you can swap VMs from one the other and have extra hardware reliability. I’d also get grouping your containers on different Docker VMs the apply the same security rules to containers in a group (internally vs. externally available for example). But how does a faulty Immich container take down a Plex container?
Could be anything.
Something decides it’s going to fill your disk up with noise and plex enters a crash loop as it can’t write to disk any more.
Your reverse proxy decides it’s not going to issue valid SSL certificates so all your plex clients refuse to connect.
One day an OS update decides your network configuration wasn’t important, and your OS throws a shit fit because there’s no route to 192.168.1.100 any more