github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

latest tag being bind to the wrong Docker image #11009

New Issue
Closed
opened 2025-11-02 09:24:49 -06:00 by GiteaMirror · 11 comments
GiteaMirror commented 2025-11-02 09:24:49 -06:00
Owner
Copy Link

Originally created by @WarningImHack3r on GitHub (Jun 10, 2023).

Description

The latest tag of your Docker image is often bind to the wrong Gitea version. I often notice that it's bind to some RC version, dev version, or currently to the 1.21.0-dev version, which is definitely not good.

I notice it because I'm running Watchtower daily to always keep my containers up-to-date, and right now my Gitea container has been bumped to this dev version and is no longer working because of an undocumented breaking change.

I can also think about the people attempting to casually download and run Gitea for the first time with a simple gitea/gitea and won't understand why it's not working.

So can you please make sure the :latest tag always points to the latest stable version please?

Gitea Version

1.21.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

latest

1 21 0

Git Version

No response

Operating System

Raspberry Pi OS 64bit

How are you running Gitea?

:latest Docker image

Database

SQLite

Originally created by @WarningImHack3r on GitHub (Jun 10, 2023). ### Description The `latest` tag of your [Docker image](https://hub.docker.com/r/gitea/gitea/tags) is often bind to the wrong Gitea version. I often notice that it's bind to some RC version, dev version, or currently to the `1.21.0-dev` version, which is definitely not good. I notice it because I'm running Watchtower daily to always keep my containers up-to-date, and right now my Gitea container has been bumped to this dev version and is no longer working because of an undocumented breaking change. I can also think about the people attempting to casually download and run Gitea for the first time with a simple `gitea/gitea` and won't understand why it's not working. So can you please make sure the `:latest` tag **always** points to the latest **stable** version please? ### Gitea Version 1.21.0 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots ![latest](https://github.com/go-gitea/gitea/assets/43064022/58f4b385-f50c-41ea-948b-df6a0b8a6f4a) --- ![1 21 0](https://github.com/go-gitea/gitea/assets/43064022/83525154-bdda-41e8-8d9f-636d81d46716) ### Git Version _No response_ ### Operating System Raspberry Pi OS 64bit ### How are you running Gitea? :latest Docker image ### Database SQLite
GiteaMirror added the type/bug label 2025-11-02 09:24:49 -06:00
GiteaMirror commented 2025-11-02 09:24:50 -06:00
Author
Owner
Copy Link

@lakoliu commented on GitHub (Jun 10, 2023):

I came hear wondering if anyone else's Gitea wasn't working. This must be the reason. My container seems to be continuously trying to restart right now.

@lakoliu commented on GitHub (Jun 10, 2023): I came hear wondering if anyone else's Gitea wasn't working. This must be the reason. My container seems to be continuously trying to restart right now.
GiteaMirror commented 2025-11-02 09:24:50 -06:00
Author
Owner
Copy Link

@WarningImHack3r commented on GitHub (Jun 10, 2023):

@lakoliu it's even more a pain that we not only have to manually downgrade but we also have to tweak/disable Watchtower temporarily because it's will bump Gitea again during its next run...

@WarningImHack3r commented on GitHub (Jun 10, 2023): @lakoliu it's even more a pain that we not only have to manually downgrade but we also have to tweak/disable Watchtower temporarily because it's will bump Gitea again during its next run...
GiteaMirror commented 2025-11-02 09:24:50 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Jun 10, 2023):

Yes, we know.
We've noticed this bug immediately when releasing 1.20.0-rc0 as the new container was pushed almost immediately from our CI.
However, we couldn't downgrade anymore without causing breakages.

@delvh commented on GitHub (Jun 10, 2023): Yes, we know. We've noticed this bug immediately when releasing 1.20.0-rc0 as the new container was pushed almost immediately from our CI. However, we couldn't downgrade anymore without causing breakages.
GiteaMirror commented 2025-11-02 09:24:51 -06:00
Author
Owner
Copy Link

@WarningImHack3r commented on GitHub (Jun 10, 2023):

@delvh I see. I assume it could only be fixed releasing a new version (1.19.x/1.20) ? Or is it even worse: not being able to fix it until a stable 1.21.0 version?

Have you planned some changes to not make it happen again? It's not the first time :latest is bind to an non-stable version

@WarningImHack3r commented on GitHub (Jun 10, 2023): @delvh I see. I assume it could only be fixed releasing a new version (1.19.x/1.20) ? Or is it even worse: not being able to fix it until a stable 1.21.0 version? Have you planned some changes to not make it happen again? It's not the first time `:latest` is bind to an non-stable version
GiteaMirror commented 2025-11-02 09:24:51 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 10, 2023):

I came hear wondering if anyone else's Gitea wasn't working. This must be the reason. My container seems to be continuously trying to restart right now.

Are you using 1.20? 1.20 has some breaking changes, could you share your logs?

@wxiaoguang commented on GitHub (Jun 10, 2023): > I came hear wondering if anyone else's Gitea wasn't working. This must be the reason. My container seems to be continuously trying to restart right now. Are you using 1.20? 1.20 has some breaking changes, could you share your logs?
GiteaMirror commented 2025-11-02 09:24:51 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Jun 10, 2023):

I assume it could only be fixed releasing a new version (1.19.x/1.20)

No, as your db will be upgraded with new versions.
You mean a stable 1.20 version, 1.21.0-dev simply means here stopped the development on 1.20 and started the development on 1.21.

@delvh commented on GitHub (Jun 10, 2023): > I assume it could only be fixed releasing a new version (1.19.x/1.20) No, as your db will be upgraded with new versions. You mean a stable 1.20 version, `1.21.0-dev` simply means here stopped the development on 1.20 and started the development on 1.21.
GiteaMirror commented 2025-11-02 09:24:51 -06:00
Author
Owner
Copy Link

@WarningImHack3r commented on GitHub (Jun 10, 2023):

@delvh so if I get it correctly it won't be fixed until 1.20.0 stable is released?

@WarningImHack3r commented on GitHub (Jun 10, 2023): @delvh so if I get it correctly it won't be fixed until 1.20.0 stable is released?
GiteaMirror commented 2025-11-02 09:24:52 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Jun 10, 2023):

Yep

@delvh commented on GitHub (Jun 10, 2023): Yep
GiteaMirror commented 2025-11-02 09:24:52 -06:00
Author
Owner
Copy Link

@WarningImHack3r commented on GitHub (Jun 10, 2023):

Have you planned some changes to not make it happen again? It's not the first time :latest is bind to an non-stable version

Ok, and about that @delvh?

@WarningImHack3r commented on GitHub (Jun 10, 2023): > Have you planned some changes to not make it happen again? It's not the first time `:latest` is bind to an non-stable version Ok, and about that @delvh?
GiteaMirror commented 2025-11-02 09:24:52 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Jun 10, 2023):

Well… We'll try to harden our CI not to set the latest tag anymore on -dev tags, but that is a trial and error process:
The only way to know it works is by releasing something, so we can only hope it won't occur next time again.

@delvh commented on GitHub (Jun 10, 2023): Well… We'll try to harden our CI not to set the `latest` tag anymore on `-dev` tags, but that is a trial and error process: The only way to know it works is by releasing something, so we can only hope it won't occur next time again.
GiteaMirror commented 2025-11-02 09:24:53 -06:00
Author
Owner
Copy Link

@WarningImHack3r commented on GitHub (Jun 10, 2023):

Don't forget -nightly, -rc* and others! 😄 Thanks for your quick response

@WarningImHack3r commented on GitHub (Jun 10, 2023): Don't forget `-nightly`, `-rc*` and others! 😄 Thanks for your quick response
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#11009
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?