Docker images for running Ubiquiti's UniFi Controller software.
I've added a check in the entrypoint that will prevent the Network Application (controller) from starting if the database files are from an older mongo and need to be upgraded. This will allow you to rollback to the container version you were using without issue. You can then schedule the upgrade when it's convenient.
Upgrade instructions are here: #95
Ubiquiti releases 'unstable', 'testing', and 'stable candidate' versions as part of its beta group release structure. These releases are included here. Only stable releases are tagged with their general version (ex: 5.6 for the 5.6.30 stable release) or with latest.
| Architecture | Available | Tag |
|---|---|---|
| amd64 | ✅ | <version tag>-amd64 |
| arm64v8 | ✅ | <version tag>-arm64v8 |
| arm32v7 | ❌ |
Note: arm32v7 is no longer supported due to a lack of upstream support for mongodb <= 3.6 for arm32/armhf
As of 7.5.x, this container image supports unifi's standard configuration utilities.
You can supply a system.properties file at /var/lib/unifi/system.properies (in the container) or set any of the following environment variables:
| Environment Variable | Description | Default |
|---|---|---|
| JVM_INIT_HEAP_SIZE | Initial Java heap size in MiB | None |
| JVM_MAX_HEAP_SIZE | Maximum Java heap size in MiB | 1024 |
| JAVA_ENTROPY_GATHER_DEVICE | Path to entropy gathering device | None |
| UNIFI_JVM_EXTRA_OPTS | Additional JVM options | $JAVA_OPTS |
Additionally, -XX:+UseParallelGC is used by default but can be changed with the unifi property unifi.G1GC.enabled.
Documentation is in the wiki.
./build.sh -v <docker version> -u <unifi version> [-t <additional docker tag> ...]
Example: ./build.sh -v 5.9.29 -u 5.9.29-04b5d20997 -t 5.9 -t 5 -t latest
./publish.sh -v <docker version> -u <unifi version>
Example: ./publish.sh -v 5.9.29 -u 5.9.29-04b5d20997
./tag.sh -v <docker version> -u <unifi version> [-t <additional docker tag> ...]
Example: ./tag.sh -v 5.9.29 -u 5.9.29-04b5d20997 -t 5.9 -t 5 -t latest