[BUG] Wrong image versions published

[mm503]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Docker image releases should reflect the sonarr release versions, however there are a few invalid versions present, which are being offered by some dependency management tools as an upgrade.

Version 5.14 (and associated tags) is being offered as an upgrade but Sonarr 5.14 does not exist. (Tags were likely related to mono 5.14)

Expected Behavior

Only valid release versions/tags should be published.

Any chance you could clean up the 5.14 tags?
https://hub.docker.com/layers/linuxserver/sonarr/5.14/images/sha256-905e718869455d834ee30ead9fb35cb93877e14d98de802a4de77d619755822d
https://hub.docker.com/layers/linuxserver/sonarr/5.14-2.0.0.5344-ls10/images/sha256-a6f5c5c00f37224d1af26c9d021143a79cd397d921ecc895a1650441e7100c32
https://hub.docker.com/layers/linuxserver/sonarr/5.14-2.0.0.5344-ls11/images/sha256-5a4293044e9b54a28af481db8ba1ce864afd487887f34b7c14e497698ea77b1f
https://hub.docker.com/layers/linuxserver/sonarr/5.14-2.0.0.5344-ls12/images/sha256-f27d0a4c24203492d215bd414ad3365e12e774e08e410747b94cff6d9856c7b2
https://hub.docker.com/layers/linuxserver/sonarr/5.14-2.0.0.5344-ls13/images/sha256-d87e41b3818558e80a21d336c9cf7c1432780bc6fb47139242c733dc7ae463f4
https://hub.docker.com/layers/linuxserver/sonarr/5.14-2.0.0.5344-ls14/images/sha256-b29de6e77a53aba34632a57924b6e97add0e49cf0f8e11186d3697b88b686c44
https://hub.docker.com/layers/linuxserver/sonarr/5.14-2.0.0.5344-ls15/images/sha256-905e718869455d834ee30ead9fb35cb93877e14d98de802a4de77d619755822d
https://hub.docker.com/layers/linuxserver/sonarr/5.14-2.0.0.5344-ls5/images/sha256-664b99a206a3beb59a84052ed8c6decb4c9d3731cadaf80bc66d9b6f1058ac78
https://hub.docker.com/layers/linuxserver/sonarr/5.14-2.0.0.5344-ls6/images/sha256-0f32625cbc7c2a9b6cf25003695571fd7f9cf118abdb903aa6a408aef0d67033
https://hub.docker.com/layers/linuxserver/sonarr/5.14-2.0.0.5344-ls7/images/sha256-f563637b2397c3a19d0f430a60c3adc37b751bdb7e33712d0a721199f8d78195
https://hub.docker.com/layers/linuxserver/sonarr/5.14-2.0.0.5344-ls8/images/sha256-fd8a638bc3dfc7a2d8fe865e95e6413cc80aa18e7379cb9824b2d0055f26b5aa
https://hub.docker.com/layers/linuxserver/sonarr/5.14-2.0.0.5344-ls9/images/sha256-e43b0f77a5f5e0f714b2431cd346a3d41b48ca704cd03612a519018ac43d7a34
https://hub.docker.com/layers/linuxserver/sonarr/5.14-version-2.0.0.5344/images/sha256-905e718869455d834ee30ead9fb35cb93877e14d98de802a4de77d619755822d

Steps To Reproduce

I run sonarr in k3s and use nova tool to find updates:

1. Deploy sonarr to kubernetes
2. Run nova find --wide --format table --containers

Alternatively you can see the issue with skopeo

$~/ skopeo list-tags docker://docker.io/linuxserver/sonarr | grep 5\.14
        "5.14",
        "5.14-2.0.0.5344-ls10",
        "5.14-2.0.0.5344-ls11",
        "5.14-2.0.0.5344-ls12",
        "5.14-2.0.0.5344-ls13",
        "5.14-2.0.0.5344-ls14",
        "5.14-2.0.0.5344-ls15",
        "5.14-2.0.0.5344-ls5",
        "5.14-2.0.0.5344-ls6",
        "5.14-2.0.0.5344-ls7",
        "5.14-2.0.0.5344-ls8",
        "5.14-2.0.0.5344-ls9",
        "5.14-version-2.0.0.5344",
        "amd64-5.14",
        "amd64-5.14-2.0.0.5344-ls10",
        "amd64-5.14-2.0.0.5344-ls11",
        "amd64-5.14-2.0.0.5344-ls12",
        "amd64-5.14-2.0.0.5344-ls13",
        "amd64-5.14-2.0.0.5344-ls14",
        "amd64-5.14-2.0.0.5344-ls15",
        "amd64-5.14-2.0.0.5344-ls5",
        "amd64-5.14-2.0.0.5344-ls6",
        "amd64-5.14-2.0.0.5344-ls7",
        "amd64-5.14-2.0.0.5344-ls8",
        "amd64-5.14-2.0.0.5344-ls9",
        "amd64-5.14-version-2.0.0.5344",
        "arm32v7-5.14",
        "arm32v7-5.14-2.0.0.5344-ls10",
        "arm32v7-5.14-2.0.0.5344-ls11",
        "arm32v7-5.14-2.0.0.5344-ls12",
        "arm32v7-5.14-2.0.0.5344-ls13",
        "arm32v7-5.14-2.0.0.5344-ls14",
        "arm32v7-5.14-2.0.0.5344-ls15",
        "arm32v7-5.14-2.0.0.5344-ls5",
        "arm32v7-5.14-2.0.0.5344-ls6",
        "arm32v7-5.14-2.0.0.5344-ls7",
        "arm32v7-5.14-2.0.0.5344-ls8",
        "arm32v7-5.14-2.0.0.5344-ls9",
        "arm32v7-5.14-version-2.0.0.5344",
        "arm64v8-5.14",
        "arm64v8-5.14-2.0.0.5344-ls10",
        "arm64v8-5.14-2.0.0.5344-ls11",
        "arm64v8-5.14-2.0.0.5344-ls12",
        "arm64v8-5.14-2.0.0.5344-ls13",
        "arm64v8-5.14-2.0.0.5344-ls14",
        "arm64v8-5.14-2.0.0.5344-ls15",
        "arm64v8-5.14-2.0.0.5344-ls5",
        "arm64v8-5.14-2.0.0.5344-ls6",
        "arm64v8-5.14-2.0.0.5344-ls7",
        "arm64v8-5.14-2.0.0.5344-ls8",
        "arm64v8-5.14-2.0.0.5344-ls9",
        "arm64v8-5.14-version-2.0.0.5344",

Environment

Kubernetes
Nova tool

CPU architecture

x86-64

Docker creation

irrelevant

Container logs

irrelevant

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[Roxedus]

We do not clean up tags, as that would hinder reproducibility.
https://www.linuxserver.io/blog/docker-tags-so-many-tags-so-little-time