docker-omada-controller VS docker-unifi-controller

I use pfSense on top of KVM, with TP-Link Omada for wifi. Rock-solid.

You can install pfSense using the serial image[1] for a real text-only console you can access via SSH to the host machine. The Omada controller runs well in docker[2].

1: https://gist.github.com/RulerOf/2608c8455b3dcf6088be206f86c6...

2: https://github.com/mbentley/docker-omada-controller

If you are Linux-savvy, you could do this even more cheaply by replacing the ER7212PC with a garden-variety PoE switch plus a Raspberry Pi 4 running Omada Controller in a Docker container, plus DHCP and DNS servers.

I have the Omada controller 4.x running on a PC. I want to move to Firewalla Purple using mbentley's Omada container, https://github.com/mbentley/docker-omada-controller

My setup: I'm using my server (HP EliteDesk 800 G2 Mini) to manage my two TP-Link Omada compatible devices (one managed switch and one Wi-Fi 6 AP) with the help of Docker - an Omada SDN wrapper image (by mbentley/docker-omada-controller). The server is running behind the managed switch (just for information), the Docker container running on this server, from docker-compose and there is no other problems just the issue below.

So if I look at his documentation, he includes a sample docker compose file here. Fantastic, I don't even have to guess or anything. I can just copy and paste his file and then tweak as necessary! Mine looks different than his because I copied his example a long time ago, and he's modified his code since then. Anyway, my service definition still works, so I'm not sweating the differences.

I have a perfect example of that. First, did you build your own unifi controller docker image, or are you using someone else's docker image like this one from linuxserver?

it's also because of the overlayfs bug. The change to load during init dropped my "startup" time on the container from 5+min to something like 9seconds. With how widespread that bug is, this was a pretty huge fix for our intended audience. https://github.com/linuxserver/docker-unifi-controller/pull/118

I plan on migrating off the UCK over to a Docker container (https://github.com/linuxserver/docker-unifi-controller) going forward. Now, the docker HOST lives in a different VLAN than the current UCK. UCK is in 192.168.1.x and the Docker host is in 192.168.3.x. I planned on making some firewall rules beforehand to allow the needed traffic to reach the host and back to my UniFi gear (USG4, 2x UAP-AC-PROs, US-8-150w, 2x USW-FLEX-MINI) so they can adopt and whatnot.

I've got my unifi controller running inside docker (https://github.com/linuxserver/docker-unifi-controller)

Trying with a second account resulted in the same error. I also tried with both 'https://github.com/jacobalberty/unifi-docker' and 'https://github.com/linuxserver/docker-unifi-controller' and they each give the same error.

Hello, I am intrested in running a virtual machine pfsense on proxmox with a unifi 6 long range, and im wondering if I would still need/find the unifi controller useful, and if something like https://github.com/linuxserver/docker-unifi-controller would suffice, since I already have home server. and also is the unifi controller also have router functionality? because while browsing through the web UI, I found things like firewall settings.

Hello, I am intrested in running a virtual pfsense with a unifi 6 long range, and im wondering if I would still need/find the unifi controller useful, and if something like https://github.com/linuxserver/docker-unifi-controller would suffice, since I already have home server.