Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 1.16.9 miss update of docker tags #20354

Closed
nemunaire opened this issue Jul 13, 2022 · 14 comments
Closed

Release 1.16.9 miss update of docker tags #20354

nemunaire opened this issue Jul 13, 2022 · 14 comments
Labels
topic/build PR changes how Gitea is built, i.e. regarding Docker or the Makefile type/bug
Milestone

Comments

@nemunaire
Copy link

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

@6543 6543 added this to the 1.16.10 milestone Jul 13, 2022
@6543 6543 added the topic/build PR changes how Gitea is built, i.e. regarding Docker or the Makefile label Jul 13, 2022
@zeripath
Copy link
Contributor

Tag 1 is not being updated by 1.16.9

1.16 should have been updated.

@zeripath
Copy link
Contributor

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

@zeripath
Copy link
Contributor

OK I've manually pushed 1.16 separately.

@nbr23
Copy link

nbr23 commented 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.

@SuNNjek
Copy link

SuNNjek commented 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?

@zeripath
Copy link
Contributor

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

@zeripath
Copy link
Contributor

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
Copy link
Contributor

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

@lunny
Copy link
Member

lunny commented 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.

@zeripath
Copy link
Contributor

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

@zeripath
Copy link
Contributor

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.

@daschu117
Copy link

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

@techknowlogick
Copy link
Member

@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
Copy link
Member

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.

@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
topic/build PR changes how Gitea is built, i.e. regarding Docker or the Makefile type/bug
Projects
None yet
Development

No branches or pull requests

8 participants