From 4d9d74252ce50a1b99599598a1958fea20f9b8e9 Mon Sep 17 00:00:00 2001 From: Quentin McGaw Date: Sat, 4 Jun 2022 10:22:05 -0400 Subject: [PATCH] Clarify docker image tags wiki --- Setup/Docker image tags.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/Setup/Docker image tags.md b/Setup/Docker image tags.md index bf7b8db..3e3c0dd 100644 --- a/Setup/Docker image tags.md +++ b/Setup/Docker image tags.md @@ -5,7 +5,7 @@ If it happens to be **broken**, this page is for you. ## Release tags -ℹ️ [Live list of image tags **after v3.9.0**](https://hub.docker.com/r/qmcgaw/gluetun/tags?page=1&ordering=last_updated) +ℹ️ [**Live list of recent image tags**](https://hub.docker.com/r/qmcgaw/gluetun/tags?page=1&ordering=last_updated) [Multiple releases](https://github.com/qdm12/gluetun/releases) are made through time when the image is considered stable. @@ -13,6 +13,11 @@ Each time a Github release is made, an associated Docker image tag is made, for You can thus use one of these image tags if `:latest` doesn't work for you. Also, don't forget to [create an issue](https://github.com/qdm12/gluetun/issues/new/choose) for it 😉 +Finally you can also use image tag `:v3` to get the latest stable release (for example `v3.28.2`), +although I would appreciate if you can use the latest image instead to detect user issues faster! + +### Older release tags + The following is for release tags before `v3.10.0`: | Image | Github release | CPU architectures |