UniFi Controller
Container
The Unifi-controller Controller software is a powerful, enterprise wireless software engine ideal for high-density client deployments requiring low latency and high uptime performance.
Image details
Configuration
TypeContainerlinuxlinuxserver/unifi-controller:latest3478:3478/udp10001:10001/udp8080:8080/tcp8081:8081/tcp8443:8443/tcp8843:8843/tcp8880:8880/tcp6789:6789/tcp/config : /portainer/Files/AppData/Config/UnifiPUID=1000PGID=100unless-stoppedTemplate by Qballjos
Standalone Install
Select an install method, to see config/commands for deploying UniFi Controller
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select UniFi Controller, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation.

The LinuxServer.io team brings you another container release featuring:
- regular and timely application updates
- easy user mappings (PGID, PUID)
- custom base image with s6 overlay
- weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
- regular security updates
Find us at:
- Blog - all the things you can do with our containers including How-To guides, opinions and much more!
- Discord - realtime support / chat with the community and the team.
- Discourse - post on our community forum.
- Fleet - an online web interface which displays all of our maintained images.
- GitHub - view the source for all of our repositories.
- Open Collective - please consider helping us by either donating or contributing to our budget
This image is deprecated. We will not offer support for this image and it will not be updated.
We recommend our unifi-network-application image instead: https://github.com/linuxserver/docker-unifi-network-applicationlinuxserver/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-\ |
| arm64 | ✅ | arm64v8-\ |
| armhf | ❌ |
Version Tags
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.| Tag | Available | Description |
|---|---|---|
| latest | ✅ | Stable Unifi Controller releases. |
| mongoless | ✅ | Stable Unifi Controller releases without mongodb included. |
Application Setup
From 2024-01-01 this image will be deprecated and it will no longer be updated. Please migrate to our Unifi Network Application image instead
See: https://info.linuxserver.io/issues/2023-09-06-unifi-controller for more information.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 > Advanced and set the Inform Host to a hostname or IP address accessible by your devices. Additionally the checkbox "Override" has to be checked, so that devices can connect to the controller during adoption (devices use the inform-endpoint during adoption).
Please note, Unifi change the location of this option every few releases so if it's not where it says, search for "Inform" or "Inform Host" in the settings.
In order to manually adopt a device take these steps:
ssh ubnt@$AP-IP
set-inform http://$address:8080/informThe 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 > networkname, to a correct (and accessable) ip address.
Strict reverse proxies
This image uses a self-signed certificate by default. This naturally means the scheme ishttps.
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=Etc/UTC
- 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-stoppeddocker cli (click here for more info)
docker run -d \
--name=unifi-controller \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Etc/UTC \
-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:latestParameters
Containers 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.| Parameter | Function |
|---|---|
-p 8443 | Unifi web admin port |
-p 3478/udp | Unifi STUN port |
-p 10001/udp | Required for AP discovery |
-p 8080 | Required for device communication |
-p 1900/udp | Required for Make controller discoverable on L2 network option |
-p 8843 | Unifi guest portal HTTPS redirect port |
-p 8880 | Unifi guest portal HTTP redirect port |
-p 6789 | For mobile throughput test |
-p 5514/udp | Remote syslog port |
-e PUID=1000 | for UserID - see below for explanation |
-e PGID=1000 | for GroupID - see below for explanation |
-e TZ=Etc/UTC | specify a timezone to use, see this list. |
-e MEMLIMIT=1024 | Optionally change the Java memory limit (in Megabytes). Set to default to reset to default |
-e MEMSTARTUP=1024 | Optionally change the Java initial/minimum memory (in Megabytes). Set to default to reset to default |
-v /config | All Unifi data stored here |
Environment variables from files (Docker secrets)
You can set any environment variable from a file by using a special prependFILE__.As an example:
-e FILE__MYVAR=/run/secrets/mysecretvariableWill set the environment variable
MYVAR based on the contents of the /run/secrets/mysecretvariable 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 your_user as below:id your_userExample output:
uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)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:
```bash
docker exec -it unifi-controller /bin/bash
```- To monitor the logs of the container in realtime:
```bash
docker logs -f unifi-controller
```- Container version number:
```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' unifi-controller
```- Image version number:
```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/unifi-controller:latest
```Updating Info
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.Below are the instructions for updating containers:
Via Docker Compose
- Update images:
* All images:
```bash
docker-compose pull
```
* Single image:
```bash
docker-compose pull unifi-controller
```- Update containers:
* All containers:
```bash
docker-compose up -d
```
* Single container:
```bash
docker-compose up -d unifi-controller
```- You can also remove the old dangling images:
```bash
docker image prune
```Via Docker Run
- Update the image:
```bash
docker pull lscr.io/linuxserver/unifi-controller:latest
```- Stop the running container:
```bash
docker stop unifi-controller
```- Delete the container:
```bash
docker rm unifi-controller
```- Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your
/configfolder and settings will be preserved) - You can also remove the old dangling images:
```bash
docker image prune
```Via Watchtower auto-updater (only use if you don't remember the original parameters)
- Pull the latest image at its tag and replace it with the same env variables in one run:
```bash
docker run --rm \
-v /var/run/docker.sock:/var/run/docker.sock \
containrrr/watchtower \
--run-once unifi-controller
```- You can also remove the old dangling images:
docker image prune
warning: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.
Image Update Notifications - Diun (Docker Image Update Notifier)
tip: We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.Building locally
If you want to make local modifications to these images for development purposes or just to customize the logic:git clone https://github.com/linuxserver/docker-unifi-controller.git
cd docker-unifi-controller
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver/unifi-controller:latest .The ARM variants can be built on x8664 hardware using
multiarch/qemu-user-staticdocker run --rm --privileged multiarch/qemu-user-static:register --resetOnce registered you can define the dockerfile to use with
-f Dockerfile.aarch64.Versions
- 01.01.24: - Deprecate.
- 05.09.23: - Add deprecation warning as per https://info.linuxserver.io/issues/2023-09-06-unifi-controller.
- 04.09.23: - Bump JRE to 17 to support v7.5.
- 02.05.23: - Cleanup
apt-get installduring build to reduce image size. - 18.03.23: - Add mongoless branch.
- 10.03.23: - Test writing to /run/unifi and symlink to /config/run if it fails.
- 20.02.23: - Migrate to s6v3, install deb package on build, fix permissions.
- 23.01.23: - Exclude
runfrom/configvolume. - 30.11.22: - Bump JRE to 11.
- 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
LTStag as Unifi no longer releases LTS stable builds. Existing users can switch to thelatesttag. 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
Serve UniFi Controller on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying unifi-controller.example.com to http://unifi-controller:8080
Add this to your Caddyfile
unifi-controller.example.com {
reverse_proxy http://unifi-controller:8080
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs unifi-controller - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:3478 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :3478 - Stop the other service, or pick a different host port. In
3478:3478only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:8080. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, unifi-controller can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 8080
Permission denied on volumes
If the logs show "permission denied", the app can't write to its data folder on the host.
- Fix the ownership:
sudo chown -R 1000:100 /portainer/Files/AppData/Config/Unifi - Or set the
PUIDandPGIDvariables (defaults 1000:100) to match your own user, found withid $USER
Image won't pull
Test the pull directly on the host: docker pull linuxserver/unifi-controller:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect unifi-controller --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue within unifi-controller's repo
- Template not working: Open an issue on Qballjos/portainer_templates
- This website not working: Open an issue on lissy93/portainer-templates
A single container
UniFi Controller runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything UniFi Controller needs bundled into one download. This template pulls linuxserver/unifi-controller:latest, which Docker fetches once (about 335 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. UniFi Controller's comes from Docker Hub, published by linuxserver.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 8.0.24. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. A mapping like 3478:3478 means it's reachable on port 3478 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:8080 in a browser. It opens:
3478:3478over UDP10001:10001over UDP8080:8080, likely the web interface8081:80818443:84438843:88438880:88806789:6789
Volumes
A volume is where UniFi Controller keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/configfrom/portainer/Files/AppData/Config/Unifion the host
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. UniFi Controller takes 2 of them, all with defaults you can leave alone or tweak:
PUID, defaults to1000PGID, defaults to100
Restart policy
The restart policy here is unless-stopped, so Docker restarts UniFi Controller after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Users and permissions
The PUID and PGID settings tell it which user and group to act as on your host. Point them at your own account (find yours with id $USER) so the files it writes into your mounted folders come out owned by you rather than root.
Networking
Nothing custom is set, so UniFi Controller sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Container name
Once it's deployed, Portainer names the container unifi-controller. That's what you'll spot in the containers list and use in commands like docker logs unifi-controller.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set UniFi Controller up. Add the template list to Portainer once, then deploying UniFi Controller is a click rather than a wall of config.