mirrors
/
AdGuardHome
mirror of https://github.com/AdguardTeam/AdGuardHome.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated info about tags

Andrey Meshkov 2020-07-10 23:31:09 +03:00
parent 575dc561b9
commit 8fca973be4
1 changed files with 2 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
Docker.md

@ -79,37 +79,14 @@ Now you can open the browser and navigate to http://127.0.0.1:3000/ to control y
## <a id="unstable"></a> Running dev builds ## <a id="unstable"></a> Running dev builds
If you want to be on the bleeding edge, you might want to run the image from the `edge` tag. It is automatically synced with the repository `master` branch. If you want to be on the bleeding edge, you might want to run the image from the `edge` or `beta` tags.
In order to use it, simply replace `adguard/adguardhome` with `adguard/adguardhome:edge` in every command from the quick start. In order to use it, simply replace `adguard/adguardhome` with `adguard/adguardhome:edge` or `adguard/adguardhome:beta` in every command from the quick start.
```bash ```bash
docker pull adguard/adguardhome:edge docker pull adguard/adguardhome:edge
``` ```
## <a id="tags"></a> Supported tags / architectures
`adguard/adguardhome` image is built for different architectures and supports the following tags:
* `latest` - latest **stable** build from the last tagged release.
* `edge` - latest build from the repository **master** branch, may be unstable.
* `$version` - specific release e.g. `v0.92`.
### Tags for different architectures
* **ARM64** - 64bit ARM build
* `arm64-latest`
* `arm64-edge`
* **ARMHF** - 32bit ARM build
* `armhf-latest`
* `armhf-edge`
* **i386** - x86 build
* `i386-latest`
* `i386-edge`
* **AMD64** - x86_64 build **default**
* `latest`
* `edge`
## <a id="configuration"></a> Additional configuration ## <a id="configuration"></a> Additional configuration
Upon the first execution, a file named `AdGuardHome.yaml` will be created, with default values written in it. You can modify the file while your AdGuard Home container is not running. Otherwise, any changes to the file will be lost because the running program will overwrite them. Upon the first execution, a file named `AdGuardHome.yaml` will be created, with default values written in it. You can modify the file while your AdGuard Home container is not running. Otherwise, any changes to the file will be lost because the running program will overwrite them.