[1.21.1] Force initial configuration on existing conf #28229
Labels
Comments
|
I can confirm that, it just happened to me too |
|
Came here to say the same. Is there a fix for this yet? (I'm going to rollback to the previous version now.) |
|
Sorry about this. There was a race condition with the release workflow that pushed the rootless image to latest. I've manually overwritten the latest tag with the appropriate information, and you can continue to pull latest now. See #28230 for more details. Please re-open if a pull of latest doesn't resolve your issue. |
techknowlogick
pushed a commit
that referenced
this issue
Dec 7, 2023
Should fix #28229 and #28230 for next release. Assuming I'm reading the docs correctly for the docker meta action: https://github.com/docker/metadata-action#flavor-input https://github.com/docker/metadata-action#latest-tag 1. We want `latest=false` for the RCs. 2. `latest` should happen already due to `auto` mode, however there's an extra option for the `suffix` flavor. This PR is ready, but leaving it as draft to make sure someone double-checks my sleuth-work. Signed-off-by: jolheiser <john.olheiser@gmail.com>
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Dec 7, 2023
Should fix go-gitea#28229 and go-gitea#28230 for next release. Assuming I'm reading the docs correctly for the docker meta action: https://github.com/docker/metadata-action#flavor-input https://github.com/docker/metadata-action#latest-tag 1. We want `latest=false` for the RCs. 2. `latest` should happen already due to `auto` mode, however there's an extra option for the `suffix` flavor. This PR is ready, but leaving it as draft to make sure someone double-checks my sleuth-work. Signed-off-by: jolheiser <john.olheiser@gmail.com>
fuxiaohei
pushed a commit
to fuxiaohei/gitea
that referenced
this issue
Jan 17, 2024
Should fix go-gitea#28229 and go-gitea#28230 for next release. Assuming I'm reading the docs correctly for the docker meta action: https://github.com/docker/metadata-action#flavor-input https://github.com/docker/metadata-action#latest-tag 1. We want `latest=false` for the RCs. 2. `latest` should happen already due to `auto` mode, however there's an extra option for the `suffix` flavor. This PR is ready, but leaving it as draft to make sure someone double-checks my sleuth-work. Signed-off-by: jolheiser <john.olheiser@gmail.com>
silverwind
pushed a commit
to silverwind/gitea
that referenced
this issue
Feb 20, 2024
Should fix go-gitea#28229 and go-gitea#28230 for next release. Assuming I'm reading the docs correctly for the docker meta action: https://github.com/docker/metadata-action#flavor-input https://github.com/docker/metadata-action#latest-tag 1. We want `latest=false` for the RCs. 2. `latest` should happen already due to `auto` mode, however there's an extra option for the `suffix` flavor. This PR is ready, but leaving it as draft to make sure someone double-checks my sleuth-work. Signed-off-by: jolheiser <john.olheiser@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
When i update to 1.21.1, it force to reconfigure gitea "Initial configuration".
When i downgrade to 1.21.0, gitea work again
Gitea Version
1.21.1
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
docker
Database
SQLite
The text was updated successfully, but these errors were encountered: