11notes/unifi repository overview

⁠UNIFI

run Unifi Controller rootless.

⁠INTRODUCTION 📢

The UniFi Network Controller is the free, central software hub for Ubiquiti's UniFi ecosystem, allowing you to discover, configure, monitor, and manage all your UniFi devices (like Access Points, Switches, Gateways) from a single, user-friendly dashboard, providing insights, performance stats, and unified control for your entire network, whether it's running on a dedicated device (Cloud Key, UDM) or installed software.

⁠CAUTION ⚠️

Do not upgrade your image directly via compose from pre 10.1.85. Version 10.1.85 is using MongoDB 8 which is not compatible with pre 10.1.85 tags at all. Backup your container data. Create a Unifi backup. Create a completely new container setup for Unifi and restore your Unifi backup. If you don’t want that dependency with a single image, checkout my Unifi Network Application image⁠ image, which separates Unifi and the DB properly.

⁠SYNOPSIS 📖

What can I do with this? This image will provide you a rock solid¹ Unifi controller with included MongoDB!

⁠UNIQUE VALUE PROPOSITION 💶

Why should I run this image and not the other image(s) that already exist? Good question! Because ...

• ... this image runs rootless⁠ as 1000:1000
• ... this image is auto updated to the latest version via CI/CD
• ... this image has a health check
• ... this image runs read-only
• ... this image is created via a secure and pinned CI/CD process

If you value security, simplicity and optimizations to the extreme, then this image might be for you.

⁠VOLUMES 📁

• /unifi/var - Directory of all configuration data and sites

⁠COMPOSE ✂️

name: "unifi"

x-lockdown: &lockdown
  # prevents write access to the image itself
  read_only: true
  # prevents any process within the container to gain more privileges
  security_opt:
    - "no-new-privileges=true"

services:
  controller:
    image: "11notes/unifi:10.4.57"
    <<: *lockdown
    environment:
      TZ: "Europe/Zurich"
    volumes:
      - "controller.var:/unifi/var"
    tmpfs:
      # needed for read only file system
      - "/unifi/log:uid=1000,gid=1000"
      - "/unifi/run:uid=1000,gid=1000"
      - "/tmp:uid=1000,gid=1000"
    ports:
      - "3000:8443/tcp"
    networks:
      frontend:
    # disable Unifi phone home function
    extra_hosts:
      - "trace.svc.ui.com:127.0.0.1"
    restart: always

volumes:
  controller.var:

networks:
  frontend:

To find out how you can change the default UID/GID of this container image, consult the RTFM⁠.

⁠DEFAULT SETTINGS 🗃️

⁠ENVIRONMENT 📝

⁠MAIN TAGS 🏷️

These are the main tags for the image. There is also a tag for each commit and its shorthand sha256 value.

• 10.4.57⁠
• 10.4.57-unraid⁠
• 10.4.57-nobody⁠

⁠There is no latest tag, what am I supposed to do about updates?

It is my opinion that the :latest tag is a bad habbit and should not be used at all. Many developers introduce breaking changes in new releases. This would messed up everything for people who use :latest. If you don’t want to change the tag to the latest semver⁠, simply use the short versions of semver⁠. Instead of using :10.4.57 you can use :10 or :10.4. Since on each new version these tags are updated to the latest version of the software, using them is identical to using :latest but at least fixed to a major or minor version. Which in theory should not introduce breaking changes.

If you still insist on having the bleeding edge release of this app, simply use the :rolling tag, but be warned! You will get the latest version of the app instantly, regardless of breaking changes or security issues or what so ever. You do this at your own risk!

⁠REGISTRIES ☁️

docker pull 11notes/unifi:10.4.57
docker pull ghcr.io/11notes/unifi:10.4.57
docker pull quay.io/11notes/unifi:10.4.57

⁠UNRAID VERSION 🟠

This image supports unraid by default. Simply add -unraid to any tag and the image will run as 99:100 instead of 1000:1000.

⁠NOBODY VERSION 👻

This image supports nobody by default. Simply add -nobody to any tag and the image will run as 65534:65534 instead of 1000:1000.

⁠SOURCE 💾

• 11notes/unifi⁠

⁠PARENT IMAGE 🏛️

• 11notes/debian:stable⁠

⁠BUILT WITH 🧰

• unifi⁠
• 11notes/util⁠

⁠GENERAL TIPS 📌

• Use a reverse proxy like Traefik, Nginx, HAproxy to terminate TLS and to protect your endpoints
• Use Let’s Encrypt DNS-01 challenge to obtain valid SSL certificates for your services

⁠DISCLAIMERS

• ¹ This image will automatically disable anonymous telemetry collected by Ubiquiti by adding a flag (config.system_cfg.1=system.analytics.anonymous=disabled) to each sites config.properties. You will still have to disable telemetry in the global settings too, to disable all telemetry. You can check your telemetry status by SSH’ing into an access point and checking grep analytics /tmp/system.cfg, the output should read disabled. Make sure not to forget the extra_hosts in your compose to prevent Unifi from phoning home.

⁠ElevenNotes™️

This image is provided to you at your own risk. Always make backups before updating an image to a different version. Check the releases⁠ for breaking changes. If you have any problems with using this image simply raise an issue⁠, thanks. If you have a question or inputs please create a new discussion⁠ instead of an issue. You can find all my other repositories on github⁠.

created 06.06.2026, 06:07:07 (CET)