I’ve usually used Gen2 Cloud Keys to run my Unifi Host Controller however in a new location I think I’m going to try to self host the controller via the linuxserver docker image: Linuxer.io Unfi Controller
Are there really any potential issues in terms of discovery or logging when self-hosting this controller? I’m considering running the docker image within a VM. Does logging consume that much space?
Myself, I run jacobalberty/unifi, but I reckon there aren’t many differences between the two as the containerize the same application.
One pitfall that comes to mind with running Unifi controller in a container is that, unless you opt for host network mode, L2 discovery won’t work. I personally can live with that since I only run it for home use and don’t need to adopt new devices all the time. Adoption is still possible using the other methods like SSH or DHCP.
I prefer to load the UniFi controller directly in the VM instead of Docker because there is not an official Docker image from UniFi which means you are trusting a third party not to put anything in there that does not belong.
Would you run into this problem if running the docker container with a macvlan network? The only issue I could think of is that each time the new container is updated, I believe it receives a different MAC address.
Thanks @LTS_Tom, @paolo and @wotsthestory for your input. I have to say after reading up on this topic of unifi controller a bit, its all kind of a mess particularly with unifi using an old version of mongodb in which support has been dropped to avoid licensing fees. Docker containers seem problematic if needing to regularly adopt containers. Tom’s solution in a video he presented used an older version of Ubuntu with I think is supported to 2028. Outside scripts such as Glen R’s, support much newer versions of Ubuntu/Debian, however then you have dependency on third parties. All kind of a mess actually and not the cleanest solution in any of the available choices.