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

Release 1.16.9 miss update of docker tags #9220

New Issue
Closed
opened 2025-11-02 08:32:30 -06:00 by GiteaMirror · 14 comments
GiteaMirror commented 2025-11-02 08:32:30 -06:00
Owner
Copy Link

Originally created by @nemunaire on GitHub (Jul 13, 2022).

Description

Docker tags gitea/gitea:1 and gitea/gitea:1.16 (+*-rootless) still point to the 1.16.8 release. They don't have been updated to point to the 1.16.9 image.

Intermediate tags, arch specific (1.16-linux-amd64, ...) are presents, so it seems it's the docker manifest step for :1.16 that's missing. Regarding :1 tag, I don't see any arch specific tag neither.

Gitea Version

1.16.9

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

image

Git Version

No response

Operating System

No response

How are you running Gitea?

Through Docker

Database

No response

Originally created by @nemunaire on GitHub (Jul 13, 2022). ### Description Docker tags [`gitea/gitea:1`](https://hub.docker.com/layers/gitea/gitea/gitea/1/images/sha256-500c844373565654b72e882becc6d9e0cc010b3c71dd8df49be7e5942eb3ce60?context=explore) and [`gitea/gitea:1.16`](https://hub.docker.com/layers/gitea/gitea/gitea/1.16/images/sha256-500c844373565654b72e882becc6d9e0cc010b3c71dd8df49be7e5942eb3ce60?context=explore) (+`*-rootless`) still point to the `1.16.8` release. They don't have been updated to point to the `1.16.9` image. Intermediate tags, arch specific ([`1.16-linux-amd64`](https://hub.docker.com/layers/gitea/gitea/gitea/1.16-linux-amd64/images/sha256-e769e9bf7cd634e83992d35b5b8c6705def2096a825f504149fa21d29f003a03?context=explore), ...) are presents, so it seems it's the docker manifest step for `:1.16` that's missing. Regarding `:1` tag, I don't see any arch specific tag neither. ### Gitea Version 1.16.9 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots ![image](https://user-images.githubusercontent.com/682394/178701107-5b544106-5b2f-46b0-ac79-c79a3539288f.png) ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Through Docker ### Database _No response_
GiteaMirror added the type/bugtopic/build labels 2025-11-02 08:32:30 -06:00
GiteaMirror commented 2025-11-02 08:32:31 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 13, 2022):

Tag 1 is not being updated by 1.16.9

1.16 should have been updated.

@zeripath commented on GitHub (Jul 13, 2022): Tag 1 is not being updated by 1.16.9 1.16 should have been updated.
GiteaMirror commented 2025-11-02 08:32:32 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 13, 2022):

what's interesting is that 1.16-linux-amd64 and 1.16-linux-arm64-rootless did get updated.

@zeripath commented on GitHub (Jul 13, 2022): what's interesting is that 1.16-linux-amd64 and 1.16-linux-arm64-rootless did get updated.
GiteaMirror commented 2025-11-02 08:32:32 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 13, 2022):

OK I've manually pushed 1.16 separately.

@zeripath commented on GitHub (Jul 13, 2022): OK I've manually pushed 1.16 separately.
GiteaMirror commented 2025-11-02 08:32:32 -06:00
Author
Owner
Copy Link

@nbr23 commented on GitHub (Jul 14, 2022):

Thanks @zeripath! Looks like only the amd64 architecture image was tagged with 1.16 btw, not the arm64.
1.16.9 has both architectures.

@nbr23 commented on GitHub (Jul 14, 2022): Thanks @zeripath! Looks like only the amd64 architecture image was tagged with 1.16 btw, not the arm64. 1.16.9 has both architectures.
GiteaMirror commented 2025-11-02 08:32:32 -06:00
Author
Owner
Copy Link

@SuNNjek commented on GitHub (Jul 14, 2022):

Is there a reason that tag "1" is not being updated to 1.16.9? It has previously pointed to the latest patch and currently points to 1.16.8. Is there an alternative tag that can be pulled to get the latest stable release instead?

@SuNNjek commented on GitHub (Jul 14, 2022): Is there a reason that tag "1" is not being updated to 1.16.9? It has previously pointed to the latest patch and currently points to 1.16.8. Is there an alternative tag that can be pulled to get the latest stable release instead?
GiteaMirror commented 2025-11-02 08:32:33 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 14, 2022):

I had been told that 1 was pointing to 1.17-rc1 but it appears that that is not the case...

@zeripath commented on GitHub (Jul 14, 2022): I had been told that 1 was pointing to 1.17-rc1 but it appears that that is not the case...
GiteaMirror commented 2025-11-02 08:32:33 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 14, 2022):

I've pushed 1.16.9 as 1.16 and 1
and I've push 1.16.9-rootless as 1.16-rootless and 1-rootless

I hope that this is everything correct now.

@zeripath commented on GitHub (Jul 14, 2022): I've pushed 1.16.9 as 1.16 and 1 and I've push 1.16.9-rootless as 1.16-rootless and 1-rootless I hope that this is everything correct now.
GiteaMirror commented 2025-11-02 08:32:33 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 14, 2022):

ugh it looks like the arm64 ones also need to be pushed... ffs.

@zeripath commented on GitHub (Jul 14, 2022): ugh it looks like the arm64 ones also need to be pushed... ffs.
GiteaMirror commented 2025-11-02 08:32:34 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jul 14, 2022):

I've pushed 1.16.9 as 1.16 and 1 and I've push 1.16.9-rootless as 1.16-rootless and 1-rootless

I hope that this is everything correct now.

You should not push to 1.

@lunny commented on GitHub (Jul 14, 2022): > I've pushed 1.16.9 as 1.16 and 1 and I've push 1.16.9-rootless as 1.16-rootless and 1-rootless > > I hope that this is everything correct now. You should not push to 1.
GiteaMirror commented 2025-11-02 08:32:34 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 14, 2022):

It was fine. 1 was pointing at 1.16.8 not 1.17-rc1.

@zeripath commented on GitHub (Jul 14, 2022): It was fine. 1 was pointing at 1.16.8 not 1.17-rc1.
GiteaMirror commented 2025-11-02 08:32:34 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 14, 2022):

The issue is that I cannot push an arm64 tag as those need manifests.

We could just release 1.16.10 once I have restored auto_tagging.

@zeripath commented on GitHub (Jul 14, 2022): The issue is that I cannot push an arm64 tag as those need manifests. We could just release 1.16.10 once I have restored auto_tagging.
GiteaMirror commented 2025-11-02 08:32:34 -06:00
Author
Owner
Copy Link

@daschu117 commented on GitHub (Jul 14, 2022):

Last night, the 1.16 tag was updated with only an amd64 image, but today it only contains an arm64/v8 image.

@daschu117 commented on GitHub (Jul 14, 2022): Last night, the 1.16 tag was updated with only an amd64 image, but today it only contains an arm64/v8 image.
GiteaMirror commented 2025-11-02 08:32:34 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jul 14, 2022):

@daschu117 Yeah, sadly working with docker manifests is troublesome. I'm attempting to get both archs copied over using the skopeo cli tool. Will update here once I have something to report.

@techknowlogick commented on GitHub (Jul 14, 2022): @daschu117 Yeah, sadly working with docker manifests is troublesome. I'm attempting to get both archs copied over using the skopeo cli tool. Will update here once I have something to report.
GiteaMirror commented 2025-11-02 08:32:35 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jul 14, 2022):

closing this as sync is done. for future reference the skopeo command I used was something like skopeo copy -a --policy temp.json docker://gitea/gitea:1.16.9-rootless docker://gitea/gitea:1-rootless for the images I updated.

@techknowlogick commented on GitHub (Jul 14, 2022): closing this as sync is done. for future reference the skopeo command I used was something like `skopeo copy -a --policy temp.json docker://gitea/gitea:1.16.9-rootless docker://gitea/gitea:1-rootless` for the images I updated.
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 topic/build 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#9220
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?