Proxmox

This method is absolutely not recommended for a container accessible with no restraints, as MongoDB 4.4 is very old and no longer contains any security updates. This is however sufficient for homelab requirements, especially as a failover node.

I faced an issue when originally trying to clone containers between proxmox nodes to add high availability to the omada controller (see Proxmox: install omada controller in high-availability). The target node would fail to start with an obscure error:

I have been using a lot of TP-Link products from the Omada series, and deployed the omada controller for centralization of the configuration (mostly for VLan configuration and wireless management). In some cases, I ended up having issues with the wifi roaming, or with the configuration because I was restarting the proxmox node on which the controller was running and no configuration could be provided.

With 6 Gigabit and 2 10G SFP interfaces available on the VEP1445 (and other VEP1400x or Edge 620-680 series), the default interface assignment of debian or proxmox is sometimes not the most convenient.

For reference the interfaces are assigned as follows on my latest Proxmox 9.0 installation