[](https://microbadger.com/images/linuxserver/unifi-controller "Get your own version badge on microbadger.com")
[](https://microbadger.com/images/linuxserver/unifi-controller "Get your own version badge on microbadger.com")
The [Unifi-controller](https://www.ubnt.com/enterprise/#unifi) Controller software is a powerful, enterprise wireless software engine ideal for high-density client deployments requiring low latency and high uptime performance.
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
This image provides various versions that are available via tags. `latest` tag provides the latest stable build from Unifi, but if this is a permanent setup you might consider using the LTS tag.
| Tag | Description |
| :----: | --- |
| latest | releases from the latest stable branch. |
| LTS | releases from the 5.6.x "LTS Stable" branch. |
| 5.9 | releases from the 5.9.x branch. |
| 5.8 | releases from the 5.8.x branch. |
| 5.7 | releases from the 5.7.x branch. |
## Common problems
When using a Security Gateway (router) it could be that network connected devices are unable to obtain an ip address. This can be fixed by setting "DHCP Gateway IP", under Settings > Networks > network_name, to a correct (and accessable) ip address.
Docker images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
When using volumes (`-v` flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
The webui is at https://ip:8443, setup with the first run wizard.
For Unifi to adopt other devices, e.g. an Access Point, it is required to change the inform ip address. Because Unifi runs inside Docker by default it uses an ip address not accessable by other devices. To change this go to Settings > Controller > Controller Settings and set the Controller Hostname/IP to an ip address accessable by other devices.
Alternatively to manually adopt a device take these steps:
```
ssh ubnt@$AP-IP
mca-cli
set-inform http://$address:8080/inform
```
Use `ubnt` as the password to login and `$address` is the IP address of the host you are running this container on and `$AP-IP` is the Access Point IP address.
## Support Info
* Shell access whilst the container is running:
*`docker exec -it unifi-controller /bin/bash`
* To monitor the logs of the container in realtime:
*`docker logs -f unifi-controller`
* Container version number
*`docker inspect -f '{{ index .Config.Labels "build_version" }}' unifi-controller`
* Image version number
*`docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/unifi-controller`
## Versions
* **10.02.19:** - Initial release of new unifi-controller image with new tags and pipeline logic
