Update the gitea docker tags to include a "stable" tag #2302

New Issue

GiteaMirror · 2025-11-02T04:31:48-06:00

GiteaMirror commented

2025-11-02 04:31:48 -06:00

Originally created by @markg85 on GitHub (Sep 6, 2018).

Hi,

I'm running gitea on docker and thus far have had no issues. My use is rather limited though ;)
One think i noticed is that the available tags [1] is either the latest git commit or one specific version. Both aren't really ideal. I'd like to have a "stable" tag which would be the same as the last released version.

So, at this very moment gitea/gitea:stable should pull in 1.5.1

[1] https://hub.docker.com/r/gitea/gitea/tags/

Originally created by @markg85 on GitHub (Sep 6, 2018). Hi, I'm running gitea on docker and thus far have had no issues. My use is rather limited though ;) One think i noticed is that the available tags [1] is either the latest git commit or one specific version. Both aren't really ideal. I'd like to have a "stable" tag which would be the same as the last released version. So, at this very moment gitea/gitea:stable should pull in 1.5.1 [1] https://hub.docker.com/r/gitea/gitea/tags/

GiteaMirror added the topic/distribution type/proposal labels 2025-11-02 04:31:48 -06:00

GiteaMirror closed this issue

2025-11-02 04:31:48 -06:00

GiteaMirror commented

2025-11-02 04:31:49 -06:00

@lafriks commented on GitHub (Sep 7, 2018):

I think gitea/gitea:1 should contain latest sable version

@lafriks commented on GitHub (Sep 7, 2018): I think `gitea/gitea:1` should contain latest sable version

GiteaMirror commented

2025-11-02 04:31:49 -06:00

@techknowlogick commented on GitHub (Sep 7, 2018):

The problem is if a release is created for 1.5.x, and some gets backported to 1.4.x and then a 1.4 release happens that would overwrite the "newer" release.

@techknowlogick commented on GitHub (Sep 7, 2018): The problem is if a release is created for 1.5.x, and some gets backported to 1.4.x and then a 1.4 release happens that would overwrite the "newer" release.

GiteaMirror commented

2025-11-02 04:31:49 -06:00

@markg85 commented on GitHub (Sep 7, 2018):

@lafriks that would be an uncommon difficult to guess way.
As far as i know, no other projects do it that way. Take a look at nginx for instance [1]

@techknowlogick then you have more maintained versions i guess.
I'd say that "stable" should probably be the version that has long terms support (if gitea even has a release that covers that). A tag like "mainline" would be the latest git version. A tag like "newest" should be the newest (and highest) release.

Anyhow, this problem has been solved by a million other projects. Take your pick in how you want to solve it ;)

[1] https://hub.docker.com/r/library/nginx/tags/

@markg85 commented on GitHub (Sep 7, 2018): @lafriks that would be an uncommon difficult to guess way. As far as i know, no other projects do it that way. Take a look at nginx for instance [1] @techknowlogick then you have more maintained versions i guess. I'd say that "stable" should probably be the version that has long terms support (if gitea even has a release that covers that). A tag like "mainline" would be the latest git version. A tag like "newest" should be the newest (and highest) release. Anyhow, this problem has been solved by a million other projects. Take your pick in how you want to solve it ;) [1] https://hub.docker.com/r/library/nginx/tags/

GiteaMirror commented

2025-11-02 04:31:50 -06:00

@lafriks commented on GitHub (Sep 12, 2018):

@techknowlogick that is quite uncommon that we would backport to more than just latest stable branch

@markg85 it is actually quite common - nginx also has :1 tag that is always same as latest 1.x.x version (https://hub.docker.com/r/library/nginx/tags/1/)

@lafriks commented on GitHub (Sep 12, 2018): @techknowlogick that is quite uncommon that we would backport to more than just latest stable branch @markg85 it is actually quite common - nginx also has `:1` tag that is always same as latest 1.x.x version (https://hub.docker.com/r/library/nginx/tags/1/)

GiteaMirror commented

2025-11-02 04:31:50 -06:00

@techknowlogick commented on GitHub (Feb 4, 2019):

Closing this as per @lafriks comment regarding :1

@techknowlogick commented on GitHub (Feb 4, 2019): Closing this as per @lafriks comment regarding `:1`

GiteaMirror commented

2025-11-02 04:31:50 -06:00

@kebertxela commented on GitHub (May 25, 2019):

Would it be possible to revisit the idea of a :stable tag?

This would allow other projects the ability to incorporate Gitea with less headache and more future proofing

@kebertxela commented on GitHub (May 25, 2019): Would it be possible to revisit the idea of a :stable tag? This would allow other projects the ability to incorporate Gitea with less headache and more future proofing

GiteaMirror commented

2025-11-02 04:31:50 -06:00

@lafriks commented on GitHub (May 25, 2019):

You can already use :1 that will be always latest stable version

@lafriks commented on GitHub (May 25, 2019): You can already use `:1` that will be always latest stable version

GiteaMirror commented

2025-11-02 04:31:51 -06:00

@kebertxela commented on GitHub (May 25, 2019):

Oh, I assumed that the :1 would only apply for Gitea versions 1.x

@kebertxela commented on GitHub (May 25, 2019): Oh, I assumed that the :1 would only apply for Gitea versions 1.x

GiteaMirror referenced this issue

2025-11-02 12:08:06 -06:00