We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. Many of container producers have such kind of disclaimer: And when something will happen, you have still fall-back to previous container ver. My guideline will take you 5 minutes from your life, without some impact to your mental health. Your backup/restore procedure of the container wasn't performed, then you lost your Unifi configuration and "default" was re-writed = DHCP.
when you have operated Unifi Controller in Docker container - you can't perform the upgrade by "standard way", as was performed by you.
Re: Adopting status (after checking of the controller update procedure above): Because when you use right Backup of Controller and Restore procedure in same way as was mentioned in my guidelines, you will get 1:1 environment with new controller version.ģ. I see some different approach here based on your description "the USG has defaulted its DHCP to 127.0.0.1, adopting status". to be sure, how did you update the controller to 5.12.66? Because when you just use every single step in my guidelines ( Resource link), you don't get any problems. this checkbox is applicable for UCK environment, or direct Controller installation to desktop PC.Ģ.
doesn't work (you need setup it by CLI set-inform for each device), in my GUI is such check box blank. checkbox 'Override inform host with controller hostname/IP'. Reason: it's up to your Network parameter configuration in docker (bridge or localhost.
When your Unifi Controller is running in Docker container (anywhere), Controller GUI settings based on: FYI, the controller version is 5.12.35.ġ. When I got the controller going again today, five of my devices were stuck on 'provisioning' and when I used SSH to connect to them and ran 'info', the set inform URL they were trying to connect to was the docker one, not the host.Īnd if anyone has seen memory creep on the UniFi controller that starts to slow the NAS down, please let me know. The external devices were connected using set-inform via SSH. I have eight internal devices on the LAN segment and two external sites with a total of three devices. My single question today though is in regards to the set-inform in the controller. Starting last night, numerous disconnections again so I blew out the container and started again. It got so bad last month I couldn't even log into the NAS and I had to force shutdown with the power button which took > 10 mins. Every couple of months though, I start getting device disconnection alarms and if left, the NAS starts to grind to halt. I've been running jacobalberty/unifi:latest for some time under Docker on my RS814+ and 95% of the time it works flawlessly. 1st time poster so I thought I'd give it a go after being encouraged on the UniFi forums.