Bot Updating Templated Files

This commit is contained in:
LinuxServer-CI 2022-05-02 22:55:48 -05:00
parent 1d31ebfb46
commit 881be6d3ab

View File

@ -46,26 +46,26 @@ Find us at:
## 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/overseerr` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/overseerr: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-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable releases from GitHub |
| develop | Development releases from commits in upstream develop branch |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable releases from GitHub |
| develop | ✅ | Development releases from commits in upstream develop branch |
## Application Setup
@ -82,7 +82,7 @@ Here are some example snippets to help you get started creating a container.
version: "2.1"
services:
overseerr:
image: lscr.io/linuxserver/overseerr
image: lscr.io/linuxserver/overseerr:latest
container_name: overseerr
environment:
- PUID=1000
@ -106,7 +106,7 @@ docker run -d \
-p 5055:5055 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/overseerr
lscr.io/linuxserver/overseerr:latest
```
## Parameters
@ -164,7 +164,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' overseerr`
* image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/overseerr`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/overseerr:latest`
## Updating Info
@ -182,7 +182,7 @@ Below are the instructions for updating containers:
### Via Docker Run
* Update the image: `docker pull lscr.io/linuxserver/overseerr`
* Update the image: `docker pull lscr.io/linuxserver/overseerr:latest`
* Stop the running container: `docker stop overseerr`
* Delete the container: `docker rm overseerr`
* Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your `/config` folder and settings will be preserved)