From 03b1737fb079c65869fd87a5cbd8098b41f57382 Mon Sep 17 00:00:00 2001 From: LinuxServer-CI Date: Tue, 3 May 2022 06:21:51 +0200 Subject: [PATCH] Bot Updating Documentation --- images/docker-unifi-controller.md | 25 +++++++++++++++---------- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/images/docker-unifi-controller.md b/images/docker-unifi-controller.md index 5387f5b490..89eb9c3c91 100644 --- a/images/docker-unifi-controller.md +++ b/images/docker-unifi-controller.md @@ -21,17 +21,17 @@ The [Unifi-controller](https://www.ubnt.com/enterprise/#unifi) software is a pow ## Supported Architectures -Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/). +We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/). -Simply pulling `lscr.io/linuxserver/unifi-controller` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +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 | Tag | -| :----: | --- | -| x86-64 | amd64-latest | -| arm64 | arm64v8-latest | -| armhf | arm32v7-latest | +| Architecture | Available | Tag | +| :----: | :----: | ---- | +| x86-64 | ✅ | amd64-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## Application Setup @@ -50,6 +50,11 @@ The default device password is `ubnt`. `$address` is the IP address of the host 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](https://docs.linuxserver.io/faq#strict-proxy). + ## Usage To help you get started creating a container from this image you can either use docker-compose or the docker cli. @@ -61,7 +66,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: unifi-controller: - image: lscr.io/linuxserver/unifi-controller + image: lscr.io/linuxserver/unifi-controller:latest container_name: unifi-controller environment: - PUID=1000 @@ -103,7 +108,7 @@ docker run -d \ -p 5514:5514/udp `#optional` \ -v :/config \ --restart unless-stopped \ - lscr.io/linuxserver/unifi-controller + lscr.io/linuxserver/unifi-controller:latest ``` ## Parameters @@ -189,7 +194,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * 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` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/unifi-controller:latest` ## Versions