goofball222/unifi repository overview

⁠UniFi Docker Container

⁠Docker tags:

• Recent changes, see: GitHub CHANGELOG.md⁠
• Report any bugs, issues or feature requests on GitHub⁠

⁠2026-10-03:

⁠UniFi Network 10.6: Final Release for Legacy USG Gateways and the Standalone Network Application⁠

Per Ubiquiti: "UniFi Network 10.6 will be the final release compatible with the legacy UniFi Security Gateway lineup (USG, USG-Pro, USG XG 8) and the legacy self-hosted/Standalone UniFi Network Application."

Barring any future 10.6 security updates and/or reversal of this decision from Ubiquiti v10.6.106⁠ will be the final release of this Docker image. I leave it up to the reader to find their own path forward with UniFi from here.

NOTE: Alpine tags DO NOT contain any internal MongoDB binaries. You must connect them to an external Mongo DB container or other host instance.

For security/attack surface reduction the container is configured to run the UniFi processes as an internal user & group unifi having a pre-set UID & GID of 999. The container will attempt to adjust permissions on mapped volumes and data to match before dropping privileges to start the UniFi Java and Mongo processes. If the container is being run with a different Docker --user setting permissions may need to be fixed manually.

IE: chown -R 999:999 ./{cert,data,logs}

A custom UID and GID can be configured for the container internal unifi user and group. For more information see the "Environment variables" section in this document.

ALWAYS MAKE A VERIFIED BACKUP OF DATA BEFORE INSTALLING UPDATES. Export a .unf from the web interface and/or stop the current container and create a backup or copy of the data volume. Database rollback from newer to older versions of UniFi and/or Mongo isn't always possible.

⁠Usage

This container exposes three volumes:

• /usr/lib/unifi/cert - SSL custom certificate storage
• /usr/lib/unifi/data - UniFi configuration data and DBs
• /usr/lib/unifi/logs - UniFi and MongoDB logs for troubleshooting

This container exposes the following ports (see: https://help.ubnt.com/hc/en-us/articles/218506997-UniFi-Ports-Used⁠):

• 3478/udp (port used for STUN connection)
• 6789/tcp (port used for throughput measurement from Android/iOS app)
• 8080/tcp (port for UAP/USW/USG to inform controller)
• 8443/tcp (port for controller GUI / API)
• 8880/tcp (port for HTTP portal redirect)
• 8843/tcp (port for HTTPS portal redirect)
• 10001/udp (port used for UBNT discovery broadcasts - Local LAN/L2/same subnet only)

The most basic way to run this container:

$ docker run --name unifi -d \
    -p 3478:3478/udp -p 8080:8080 -p 8443:8443 \
    -p 8880:8880 -p 8843:8843 \
    ghcr.io/goofball222/unifi

Recommended run method: Docker Compose⁠ - UniFi app and internal Mongo DB:

version: '3'

services:
  unifi:
    image: ghcr.io/goofball222/unifi
    container_name: unifi
    restart: unless-stopped
    network_mode: bridge
    ports:
      - 3478:3478/udp
      - 8080:8080
      - 8443:8443
      - 8880:8880
      - 8843:8843
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ./cert:/usr/lib/unifi/cert
      - ./data:/usr/lib/unifi/data
      - ./logs:/usr/lib/unifi/logs
    environment:
      - TZ=UTC

Recommended run method: Docker Compose⁠ - UniFi app and Mongo DB as separate services:

version: '3'

services:
  mongo:
#   Use max mongo version 8.0.X. Higher versions are not recommended by Ubiquiti/UniFi.
#   Older versions are acceptable, ie: mongo:7.0
    image: mongo:8.0
    container_name: unifidb
    restart: unless-stopped
#   By default docker-compose will create a new bridge network for the services in the compose file.
#   Enable this to have the services/containers use the existing docker0/default bridge network.
#    network_mode: bridge
    volumes:
      - ./data/db:/data/db

  unifi:
    image: ghcr.io/goofball222/unifi
    container_name: unifi
    restart: unless-stopped
#   By default docker-compose will create a new bridge network for the services in the compose file.
#   Enable this to have the services/containers use the existing docker0/default bridge network.
#    network_mode: bridge
    links:
      - mongo
    ports:
      - 3478:3478/udp
      - 8080:8080
      - 8443:8443
      - 8880:8880
      - 8843:8843
#     Optional: Uncomment to enable speed tests from the UniFi iOS & Android apps
#      - 6789:6789
#     Optional: Uncomment for layer 2 broadcast discovery if container running on a host in the local LAN
#      - 10001:10001/udp
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ./cert:/usr/lib/unifi/cert
      - ./data:/usr/lib/unifi/data
      - ./logs:/usr/lib/unifi/logs
    environment:
      - DB_MONGO_LOCAL=false
      - DB_MONGO_URI=mongodb://mongo:27017/unifi
      - STATDB_MONGO_URI=mongodb://mongo:27017/unifi_stat
      - TZ=UTC
      - UNIFI_DB_NAME=unifi

Alternative network setup suggested by rogierlommers⁠ -

Please make sure to read the "NETWORK: HOST" section of the Docker "run" reference⁠ and understand the implications of this before using.

Copy the following to both services in the docker-compose.yml file under the commented out network_mode: bridge line in the example above, and then uncomment the network_mode: host line:

#   Use host network mode. Does not allow for port remapping. You may need to manually adjust
#       host firewall settings to allow traffic. Running a container in this mode is considered insecure.
#    network_mode: host

Example basic docker-compose.yml in file form⁠.

Example advanced docker-compose.yml in file form⁠ with external Mongo DB service and UniFi service using environment variables.

Environment variables:

Recommended UniFi system.properties converted environment variables to externalize Mongo DB via docker-compose:

NB/IMPORTANT: Although I've been running my own deployments with an external DB without issue with these settings externalizing the DB, just like running the app itself in a Docker container, is considered experimental and totally unsupported by UBNT. Full documentation for an external DB setup is outside the scope of this README and is left as an exercise for the interested reader. Additional information available on the UBNT forums in this post⁠ and in the PDF post linked below.

Additional UniFi system.properties⁠ config file settings can be passed to the container as -e/--env/environment flags at runtime (more detail and a PDF with UBNT examples here)⁠. Envrionment variables must be in ALL CAPS and replace "." with "_". -- IE:

SSL custom certificate auto-configuration support (LetsEncrypt⁠, etc.):

1. Map the Docker host cert storage location or volume to the /usr/lib/unifi/cert volume exposed by the container
2. Must contain a PEM format SSL private key corresponding to the SSL certificate to be installed. Private key file MUST be named privkey.pem.
3. Must contain a PEM format SSL certificate file. Certificate file MUST be named cert.pem.
   • For versions prior to 7.3, the SSL certificate file MUST be named fullchain.pem and must contain the full certification chain. LetsEncrypt handles this automatically, other providers may need manual work (https://www.digicert.com/ssl-support/pem-ssl-creation.htm⁠).
4. Start the container. SSL import and Java keystore update process is automated during startup. Status, errors, etc. can be found in the container log, IE: docker logs "containername"
5. Existing keystore file will be backed up to /usr/lib/unifi/data/keystore-"epochseconds"
6. Java keystore is only updated when changes to the certificate files are detected. To force a re-import of existing files delete the unificert.sha256 file in ./cert and restart the container.

If you don't want to use a custom SSL certificate then the /usr/lib/unifi/cert volume can be left unmapped. Alternatively if the privkey.pem and/or fullchain.pem file are not present SSL customization will be skipped.

To revert from a custom cert to a UniFi self-signed certificate stop the container, rename or remove ./data/keystore, and restart the container. The UniFi application will automatically generate a new keystore file with a new self-signed cert.

⁠beta and bleeding-edge official tag warning

NOT RECOMMENDED FOR USE IN A PRODUCTION ENVIRONMENT - FOR TESTING/LABS ONLY

There have been past UniFi beta and official releases with AP bricking firmware, network breaking bugs, etc.

Proceed with caution! Use at your own risk.

If you're going to use these images please make sure you create a UBNT community account: https://community.ui.com/⁠

Instructions for how to sign up for beta/early access at: https://help.ui.com/hc/en-us/articles/204908664-How-To-Sign-Up-for-Early-Access⁠

Please make sure to participate in discussion and create bug reports for any issues you encounter with beta/early access releases.

USE BETA/BLEEDING-EDGE RELEASES AT YOUR OWN RISK - REPEAT: NOT RECOMMENDED FOR USE IN A PRODUCTION ENVIRONMENT WITHOUT EXTENSIVE TESTING

This project is not affiliated with, endorsed by, or supported by Ubiquiti Inc. All trademarks and copyrights belong to their respective owners.