docker-unifi-controller VS unifi-docker

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.

The other: https://github.com/jacobalberty/unifi-docker

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.

> I just stopped updating the controller software (none of their gear is external-facing, and IIRC it's only needed for configuration/management) because cloud login is an absolute dealbreaker for me.

Yeah. Updates used to be a nightmare. I had to worry about Windows updates, Java updates, and of course Unifi updates.

Then I started to use the Docker container at https://github.com/jacobalberty/unifi-docker

I have 21 APs all controlled by the container on a Raspberry Pi 4. It's not even breaking a sweat. When I want to upgrade the Unifi application, I stop the container, and re-run the command to use the newer Unifi version. Three minutes later, it's back on the air.

https://github.com/jacobalberty/unifi-docker/issues/525 loks like it jist needs some adjustments.

Link to the issue on github rather than retyping everything: https://github.com/jacobalberty/unifi-docker/issues/540

Check out https://github.com/jacobalberty/unifi-docker

What image? if you are using jacobalberty/unifi I updated the v5.4.23 tag early this morning to include the latest fix for log4shell. I would be willing to backport the fix to a specific version if you want, see this issue and post there requesting it. If you are using the linuxserver image, I'm not familiar enough with that one to help you out. When I get some free time I may look into porting the fix to their image customization setup (which looks nice) but that free time is unfortunately like a week away.

No problems, but only a couple sites on it. Currently running 6.0.45. https://github.com/jacobalberty/unifi-docker