Bottom Line: For a New UniFi Deployment, Follow Ubiquiti's Current Self-Hosting Model Rather Than a 2024 BigBear Container Template
The 2024 CasaOS post pointed users to a BigBearCasaOS package for the UniFi Network Application. Ubiquiti's current self-hosting story has changed: it now promotes UniFi OS Server for supported Linux/Windows/macOS self-hosting, and explicitly says the complete UniFi OS Server is not available as a standalone Docker/Podman container because discovery, adoption and updates rely on host services. That makes an old community container a legacy path, not the default 2026 recommendation.
Choose the Right UniFi Product First
If you already own a UniFi Cloud Gateway such as a UDM or UCG, it already includes the UniFi Network control plane and should not be adopted by an external self-hosted controller. If you use independent gateways, switches and access points, a self-hosted UniFi server can be appropriate.
Ubiquiti's UniFi self-hosting describes this boundary.
Prefer a Dedicated Linux VM for ZimaOS Hosts
Because current UniFi OS Server expects host-level services rather than a single Docker container, a small Debian/Ubuntu VM is a cleaner fit on ZimaOS than forcing the full server into the NAS host. This isolates updates, Java/Mongo/service dependencies and network discovery from the ZimaOS appliance.
The ZimaOS VM requirements provides the ZimaOS-side resource model.
Open the Required Network Ports Deliberately
UniFi device discovery/adoption depends on more than the web UI. Ubiquiti lists ports including UDP 3478, UDP 10001 and TCP 8080 for classic Network Application workflows, with additional ports depending on remote access and features. The UniFi required ports is the current port reference.
Keep Controller and Devices Reachable at Adoption Time
If access points or switches are on another VLAN/subnet, Layer-2 discovery may not work. Use a deliberate remote-adoption method and ensure routing/firewall policy permits the required control traffic. Do not solve discovery by opening every UniFi port to the public internet.
Back Up the UniFi Site Before Updates
Ubiquiti recommends downloading a backup before updating a self-hosted Network server. Keep a copy outside the VM/system disk. The ZimaOS backup provides the NAS-level recovery layer.
Why the Old Docker Package Can Still Work
Community container images for the classic UniFi Network Application may still run for some users. That does not make them equivalent to current UniFi OS Server support. If you intentionally keep one, pin versions, persist database/config data and follow the image maintainer's update instructions.
Do Not Expose the Admin Interface Directly Without HTTPS
Network-controller credentials can change Wi-Fi, gateways and VLANs. Keep the admin endpoint LAN/VPN-only where possible. If it must be public, use strong authentication, TLS and restricted source access. The ZimaOS HTTPS proxying covers the public web boundary.
When to Use a UniFi Console Instead
If network management is mission-critical and you want Ubiquiti's integrated update/support path, a UniFi Cloud Gateway or Console is operationally simpler than self-hosting. Choose ZimaOS-hosted UniFi when you specifically want to operate the controller infrastructure yourself.
Plan Adoption Before Moving an Existing UniFi Site
If devices are already adopted by another controller, do not simply start a second server and expect it to take over. Export a site/system backup, record the current inform/control address, and use Ubiquiti's supported migration/adoption process. A controller move should preserve device ownership, WLAN/VLAN settings and certificates rather than forcing every access point back to factory defaults.
FAQ
Can I still install UniFi with BigBearCasaOS?
Legacy community packages may exist, but current Ubiquiti self-hosting guidance should be the baseline for a new deployment.
Can UniFi OS Server run in Docker?
Ubiquiti currently says the complete UniFi OS Server is not offered as a standalone Docker/Podman container.
Should I run UniFi in a ZimaOS VM?
A dedicated Linux VM provides a clean host boundary for current self-hosted UniFi services.
Which ports must be open?
Use Ubiquiti's current required-ports reference and expose only the ports needed for discovery, adoption and management.
Do I need a self-hosted controller with a UDM or UCG?
No. Current UniFi Cloud Gateways already include the UniFi Network control plane.
