linuxserver/unifi-controller

​linuxserver/unifi-controller​
​​
​ ​
​ ​
​ ​
​ ​
​ ​
​ ​
​ ​
​ ​
​ ​
​​
The Unifi-controller software is a powerful, enterprise wireless software engine ideal for high-density client deployments requiring low latency and high uptime performance.
Supported Architectures
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/unifi-controller:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
Architecture
Available
Tag
x86-64
✅
amd64-<version tag>
arm64
✅
arm64v8-<version tag>
armhf
❌
​
Application Setup
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 accessible by other devices. To change this go to Settings > System Settings > Controller Configuration and set the Controller Hostname/IP to a hostname or IP address accessible by your devices. Additionally the checkbox "Override inform host with controller hostname/IP" has to be checked, so that devices can connect to the controller during adoption (devices use the inform-endpoint during adoption).
In order to manually adopt a device take these steps:
ssh [email protected]$AP-IP
set-inform http://$address:8080/inform
The default device password is ubnt. $address is the IP address of the host you are running this container on and $AP-IP is the Access Point IP address.
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.
Strict reverse proxies
This image uses a self-signed certificate by default. This naturally means the scheme is https. If you are using a reverse proxy which validates certificates, you need to disable this check for the container.
Usage
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
docker-compose (recommended, click here for more info)
---
version: "2.1"
services:
  unifi-controller:
    image: lscr.io/linuxserver/unifi-controller:latest
    container_name: unifi-controller
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      - MEM_LIMIT=1024 #optional
      - MEM_STARTUP=1024 #optional
    volumes:
      - <path to data>:/config
    ports:
      - 8443:8443
      - 3478:3478/udp
      - 10001:10001/udp
      - 8080:8080
      - 1900:1900/udp #optional
      - 8843:8843 #optional
      - 8880:8880 #optional
      - 6789:6789 #optional
      - 5514:5514/udp #optional
    restart: unless-stopped
docker cli (click here for more info)
docker run -d \
  --name=unifi-controller \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -e MEM_LIMIT=1024 `#optional` \
  -e MEM_STARTUP=1024 `#optional` \
  -p 8443:8443 \
  -p 3478:3478/udp \
  -p 10001:10001/udp \
  -p 8080:8080 \
  -p 1900:1900/udp `#optional` \
  -p 8843:8843 `#optional` \
  -p 8880:8880 `#optional` \
  -p 6789:6789 `#optional` \
  -p 5514:5514/udp `#optional` \
  -v <path to data>:/config \
  --restart unless-stopped \
  lscr.io/linuxserver/unifi-controller:latest
Parameters
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.
Ports (-p)
Parameter
Function
8443
Unifi web admin port
3478/udp
Unifi STUN port
10001/udp
Required for AP discovery
8080
Required for device communication
1900/udp
Required for Make controller discoverable on L2 network option
8843
Unifi guest portal HTTPS redirect port
8880
Unifi guest portal HTTP redirect port
6789
For mobile throughput test
5514/udp
Remote syslog port
Environment Variables (-e)
Env
Function
PUID=1000
for UserID - see below for explanation
PGID=1000
for GroupID - see below for explanation
TZ=Europe/London
Specify a timezone to use (e.g. Europe/London) - see list​
MEM_LIMIT=1024
Optionally change the Java memory limit. Set to default to reset to default
MEM_STARTUP=1024
Optionally change the Java initial/minimum memory. Set to default to reset to default
Volume Mappings (-v)
Volume
Function
/config
All Unifi data stored here
Miscellaneous Options
Environment variables from files (Docker secrets)
You can set any environment variable from a file by using a special prepend FILE__.
As an example:
-e FILE__PASSWORD=/run/secrets/mysecretpassword
Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.
Umask for running applications
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
User / Group Identifiers
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.
In this instance PUID=1000 and PGID=1000, to find yours use id user as below:
  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
Docker Mods
​​
​ ​
​​
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
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" }}' lscr.io/linuxserver/unifi-controller:latest
Versions
01.06.22: - Deprecate armhf.
23.12.21: - Move min/max memory config from run to system.properties.
22.12.21: - Move deb package install to first init to avoid overlayfs performance issues.
13.12.21: - Rebase 64 bit containers to Focal.
11.12.21: - Add java opts to mitigate CVE-2021-44228.
11.06.21: - Allow for changing Java initial mem via new optional environment variable.
12.01.21: - Deprecate the LTS tag as Unifi no longer releases LTS stable builds. Existing users can switch to the latest tag. Direct upgrade from 5.6.42 (LTS) to 6.0.42 (latest) tested successfully.
17.07.20: - Rebase 64 bit containers to Bionic and Mongo 3.6.
16.06.20: - Add logrotate.
02.06.20: - Updated port list & descriptions. Moved some ports to optional.
14.11.19: - Changed url for deb package to match new Ubiquity domain.
29.07.19: - Allow for changing Java mem limit via new optional environment variable.
23.03.19: - Switching to new Base images, shift to arm32v7 tag.
10.02.19: - Initial release of new unifi-controller image with new tags and pipeline logic

Images - Previous

linuxserver/ubooquity

Next - Images

linuxserver/webgrabplus

Last modified 4d ago

Copy link

On this page

linuxserver/unifi-controller

Supported Architectures

Application Setup

Usage

Parameters

Environment variables from files (Docker secrets)

Umask for running applications

User / Group Identifiers

Docker Mods

Support Info

Versions

linuxserver/unifi-controller

Supported Architectures

Application Setup

Strict reverse proxies

Usage

docker-compose (recommended, click here for more info)

docker cli (click here for more info)

Parameters

Ports (`-p`)

Environment Variables (`-e`)

Volume Mappings (`-v`)

Environment variables from files (Docker secrets)

Umask for running applications

User / Group Identifiers

Docker Mods

Support Info

Versions

​linuxserver/unifi-controller​

Supported Architectures

Application Setup

Strict reverse proxies

Usage

docker-compose (recommended, click here for more info)

docker cli (click here for more info)

Parameters

Ports (-p)

Environment Variables (-e)

Volume Mappings (-v)

Environment variables from files (Docker secrets)

Umask for running applications

User / Group Identifiers

Docker Mods

Support Info

Versions

linuxserver/unifi-controller

Ports (`-p`)

Environment Variables (`-e`)

Volume Mappings (`-v`)