From f68cf87bcb89cf5d510cf03254d26462a911be0d Mon Sep 17 00:00:00 2001 From: LinuxServer-CI Date: Thu, 5 May 2022 13:32:32 +0200 Subject: [PATCH] Bot Updating Templated Files --- README.md | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/README.md b/README.md index 1c6865e..996d5bf 100644 --- a/README.md +++ b/README.md @@ -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/beets` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/beets: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-\ | ## 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 Beets Releases | -| nightly | Built against head of Beets git, generally considered unstable but a likely choice for power users of the application. | +| Tag | Available | Description | +| :----: | :----: |--- | +| latest | ✅ | Stable Beets Releases | +| nightly | ✅ | Built against head of Beets git, generally considered unstable but a likely choice for power users of the application. | ## Application Setup @@ -90,7 +90,7 @@ Here are some example snippets to help you get started creating a container. version: "2.1" services: beets: - image: lscr.io/linuxserver/beets + image: lscr.io/linuxserver/beets:latest container_name: beets environment: - PUID=1000 @@ -118,7 +118,7 @@ docker run -d \ -v :/music \ -v :/downloads \ --restart unless-stopped \ - lscr.io/linuxserver/beets + lscr.io/linuxserver/beets:latest ``` ## Parameters @@ -178,7 +178,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' beets` * image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/beets` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/beets:latest` ## Updating Info @@ -196,7 +196,7 @@ Below are the instructions for updating containers: ### Via Docker Run -* Update the image: `docker pull lscr.io/linuxserver/beets` +* Update the image: `docker pull lscr.io/linuxserver/beets:latest` * Stop the running container: `docker stop beets` * Delete the container: `docker rm beets` * 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)