-
Notifications
You must be signed in to change notification settings - Fork 32
Getting Started
UniFi OS Server is more resource intensive than the Network Controller and requires sufficient CPU/RAM to function. Many connected devices will require more resources.
- x86_64 or ARM64 CPU
- At least 2GB RAM
- 20GB free disk space
- Docker Compose >v2
- Linux Kernel >3.16
Use the docker-compose.yaml template and update /path/to/unifi-os-server/* to your host's persistent data paths.
After starting the container, the UniFi OS Server console will be available at https://<IP>:11443.
See kubernetes/.
Note that currently Kubernetes deployments require privileged: true in order to function. See #51.
If you're changing the inform address by migrating to a different host or new IP/domain, you may want to update your UniFi devices' set-inform address before migration.
The easiest way to migrate from UniFi Network Controller to UniFi OS Server is to use backup and restore:
- Backup Network Controller config
- Shutdown Network Controller
- Start UniFi OS Server
- Select Restore from Backup on the setup page and upload your
.unfbackup file
To migrate from a standard installation of UniFi OS Server (as provided by UniFi), follow the same backup and restore steps as above.
If your backup file is from a newer Network version than what's bundled with UniFi OS Server, restore will not work. You will first need to:
- Setup UniFi OS Server without restore, using a temporary local user
- Navigate to Settings > Control Plane > Updates and update Network
- Restore backup from Settings > Control Plane > Backups > Restore
To update UniFi OS Server, use docker pull ghcr.io/lemker/unifi-os-server:latest or update the pinned tag in your Docker Compose file. You may wish to setup alerts for when new releases are published on GitHub or use a GitOps method like Renovate to keep your container updated.
To update UniFi applications like Network, InnerSpace, etc. use the UniFi OS Server GUI: navigate to Settings > Control Plane > Updates