kopia lustrzana https://github.com/linuxserver/docker-documentation
Bot Updating Templated Files
LinuxServer-CI
rodzic
221e3c96d5
commit
c86fc34ab7
|
|
@ -1,9 +1,16 @@
|
|||
# linuxserver/unifi-controller
|
||||
# [linuxserver/unifi-controller](https://github.com/linuxserver/docker-unifi-controller)
|
||||
|
||||
[](https://github.com/linuxserver/docker-unifi-controller/releases) [](https://microbadger.com/images/linuxserver/unifi-controller) [](https://microbadger.com/images/linuxserver/unifi-controller) [](https://hub.docker.com/r/linuxserver/unifi-controller) [](https://hub.docker.com/r/linuxserver/unifi-controller) [](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-unifi-controller/job/master/) [](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/unifi-controller/latest/index.html)
|
||||
[](https://github.com/linuxserver/docker-unifi-controller/releases)
|
||||
[](https://microbadger.com/images/linuxserver/unifi-controller "Get your own version badge on microbadger.com")
|
||||
[](https://microbadger.com/images/linuxserver/unifi-controller "Get your own version badge on microbadger.com")
|
||||
[](https://hub.docker.com/r/linuxserver/unifi-controller)
|
||||
[](https://hub.docker.com/r/linuxserver/unifi-controller)
|
||||
[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-unifi-controller/job/master/)
|
||||
[](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/unifi-controller/latest/index.html)
|
||||
|
||||
The [Unifi-controller](https://www.ubnt.com/enterprise/#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
|
||||
|
||||
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/).
|
||||
|
|
@ -13,18 +20,19 @@ Simply pulling `linuxserver/unifi-controller` should retrieve the correct image
|
|||
The architectures supported by this image are:
|
||||
|
||||
| Architecture | Tag |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| x86-64 | amd64-latest |
|
||||
| arm64 | arm64v8-latest |
|
||||
| armhf | arm32v7-latest |
|
||||
|
||||
|
||||
## Usage
|
||||
|
||||
Here are some example snippets to help you get started creating a container from this image.
|
||||
|
||||
### docker
|
||||
|
||||
```text
|
||||
```
|
||||
docker create \
|
||||
--name=unifi-controller \
|
||||
-e PUID=1000 \
|
||||
|
|
@ -47,17 +55,17 @@ docker create \
|
|||
|
||||
This image provides various versions that are available via tags. `latest` tag provides the latest stable build from Unifi, but if this is a permanent setup you might consider using the LTS tag.
|
||||
|
||||
| Tag | Description |
|
||||
| :---: | :--- |
|
||||
| latest | releases from the latest stable branch. |
|
||||
| LTS | releases from the 5.6.x "LTS Stable" branch. |
|
||||
| 5.9 | releases from the now EOL 5.9.x branch. |
|
||||
| 5.8 | releases from the now EOL 5.8.x branch. |
|
||||
| 5.7 | releases from the now EOL 5.7.x branch. |
|
||||
| Tag | Description |
|
||||
| :----: | -------------------------------------------- |
|
||||
| latest | releases from the latest stable branch. |
|
||||
| LTS | releases from the 5.6.x "LTS Stable" branch. |
|
||||
| 5.9 | releases from the now EOL 5.9.x branch. |
|
||||
| 5.8 | releases from the now EOL 5.8.x branch. |
|
||||
| 5.7 | releases from the now EOL 5.7.x branch. |
|
||||
|
||||
## Common problems
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
### docker-compose
|
||||
|
||||
|
|
@ -90,12 +98,12 @@ services:
|
|||
|
||||
## Parameters
|
||||
|
||||
Docker images 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.
|
||||
Docker images 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.
|
||||
|
||||
### Ports \(`-p`\)
|
||||
### Ports (`-p`)
|
||||
|
||||
| Parameter | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `3478/udp` | Unifi communication port |
|
||||
| `10001/udp` | required for AP discovery |
|
||||
| `8080` | required for Unifi to function |
|
||||
|
|
@ -105,42 +113,45 @@ Docker images are configured using parameters passed at runtime \(such as those
|
|||
| `8880` | Unifi communication port |
|
||||
| `6789` | For throughput test |
|
||||
|
||||
### Environment Variables \(`-e`\)
|
||||
|
||||
### Environment Variables (`-e`)
|
||||
|
||||
| Env | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `PUID=1000` | for UserID - see below for explanation |
|
||||
| `PGID=1000` | for GroupID - see below for explanation |
|
||||
| `MEM_LIMIT=1024M` | Optionally change the Java memory limit \(-Xmx\) \(default is 1024M\). |
|
||||
| `MEM_LIMIT=1024M` | Optionally change the Java memory limit (-Xmx) (default is 1024M). |
|
||||
|
||||
### Volume Mappings \(`-v`\)
|
||||
### Volume Mappings (`-v`)
|
||||
|
||||
| Volume | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `/config` | All Unifi data stored here |
|
||||
|
||||
|
||||
|
||||
## 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`.
|
||||
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 user` as below:
|
||||
|
||||
```text
|
||||
```
|
||||
$ id username
|
||||
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
||||
```
|
||||
|
||||
## Application Setup
|
||||
|
||||
The webui is at [https://ip:8443](https://ip:8443), setup with the first run wizard.
|
||||
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 accessable by other devices. To change this go to Settings > Controller > Controller Settings and set the Controller Hostname/IP to an ip address accessable by other devices.
|
||||
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 accessable by other devices. To change this go to Settings > Controller > Controller Settings and set the Controller Hostname/IP to an ip address accessable by other devices.
|
||||
|
||||
Alternatively to manually adopt a device take these steps:
|
||||
|
||||
```text
|
||||
```
|
||||
ssh ubnt@$AP-IP
|
||||
mca-cli
|
||||
set-inform http://$address:8080/inform
|
||||
|
|
@ -148,6 +159,8 @@ set-inform http://$address:8080/inform
|
|||
|
||||
Use `ubnt` as the password to login and `$address` is the IP address of the host you are running this container on and `$AP-IP` is the Access Point IP address.
|
||||
|
||||
|
||||
|
||||
## Support Info
|
||||
|
||||
* Shell access whilst the container is running:
|
||||
|
|
@ -164,4 +177,3 @@ Use `ubnt` as the password to login and `$address` is the IP address of the host
|
|||
* **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
|
||||
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue