Your UniFi Network Application does not need its own 192.168.x.x address just because Docker gives the container a 172.x bridge address. In normal bridge mode, publish the required host ports and configure UniFi's Inform Host to a LAN-reachable hostname or IP. Devices on the LAN talk to the host address, while Docker keeps the container on its private network.
The 2026 source thread mixed up the container's internal bridge IP with the address LAN devices should use. Current LinuxServer documentation explicitly covers this: the UniFi container can stay bridged, and device adoption is handled by setting an accessible Inform Host and preserving port 8080.
Why You See a 172.x Address
Docker bridge networks normally assign private container addresses such as 172.17.x.x. That address is for container networking, not the address your switches and access points must use from the physical LAN.
Use the ZimaOS Host IP for Published Ports
If the ZimaOS server is 192.168.1.20 and UniFi publishes 8443 and 8080, you access the UI and inform endpoint through the host:
https://192.168.1.20:8443
http://192.168.1.20:8080/informSet the UniFi Inform Host
The current LinuxServer UniFi documentation says Docker users should set the Inform Host/Override to a hostname or IP reachable by UniFi devices.
That is usually the ZimaOS LAN IP or a stable local DNS name.
Keep Port 8080 Mapped 1:1
LinuxServer warns that UniFi device communication expects 8080:8080 unless you also make matching changes inside UniFi's system properties. Do not casually map host 18080 to container 8080 and expect adoption to remain stable.
Host Mode Is Not the Same as “Give the Container Its Own LAN IP”
Docker host mode makes the container share the host's network namespace. It does not create a second 192.168.x.x address for the container.
If you truly need a separate LAN IP, that is a macvlan/ipvlan design, which adds routing and host-to-container communication caveats.
Bridge Mode Is Usually the Simpler Choice
Bridge mode keeps the app isolated, makes port ownership explicit, and works with the documented Inform Host override. It is usually enough for controller adoption and management.
Remember the External MongoDB Requirement
Current LinuxServer UniFi Network Application requires an external MongoDB instance. If host mode fails while bridge mode works, confirm the MongoDB hostname and network path remain valid under the selected network mode.
Do Not Expose the Controller Directly to the Internet
Keep management on the LAN or behind a private remote-access network. The private network guide provides the safer networking context.
Use a Stable Host Address
Because adopted devices are told where to find the controller, give the ZimaOS host a stable LAN IP through a router DHCP reservation or a carefully managed static address. If the controller host changes from 192.168.1.20 to another address, devices can continue contacting the old inform endpoint.
Understand Which Ports Are for Which Job
The UniFi web interface on 8443 is only one piece. Device inform traffic uses 8080, and other discovery/STUN services use additional ports depending on the deployment. A controller can therefore appear healthy in a browser while devices fail adoption.
Use the current LinuxServer port table and expose only what your environment needs, but preserve the required device-management ports exactly.
Restore from Synology Carefully
If you are migrating the controller from Synology, restore a UniFi backup only after the new ZimaOS container and external MongoDB are healthy. Then verify Inform Host and device status before shutting down the old controller.
Do not run two active controllers claiming the same sites/devices during migration unless you understand the adoption consequences.
When a Dedicated LAN IP Is Actually Useful
A macvlan/ipvlan address can be useful for strict firewall segmentation, port-collision avoidance, or making the controller look like a separate appliance. It is not required simply because Docker displays a 172.x internal address.
If you choose macvlan, plan for the common host-to-macvlan communication limitation and verify that MongoDB remains reachable from the controller network.
FAQ
Does the UniFi container need a 192.168 LAN IP?
No. Bridge mode plus published ports and a reachable Inform Host is sufficient in many deployments.
Why do UniFi devices fail adoption in Docker?
A common cause is advertising an unreachable container IP. Set the Inform Host to the ZimaOS LAN address or another reachable hostname.
Should I use host networking?
Only if you have a reason. Host mode shares the ZimaOS host network; it does not create a dedicated LAN IP.
When should I use macvlan?
Use it only when the container truly needs its own LAN identity and you understand the extra routing and host-access complexity.
