-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
corrupted container package #21736
Comments
You can delete all packages from admin panel -> packages |
You do not need to delete all packages. Just delete the failing package (and all other images which share the missing blobs). Then add/modify your [cron.cleanup_packages]
;; Unreferenced blobs created more than OLDER_THAN ago are subject to deletion
OLDER_THAN = 1s Then you can run the package cleanup job from the admin panel to remove the non-existing package blobs from the database. After that you should be able to upload the package again. Or you delete the missing blobs from the |
Running cron solved this, thanks. My issue is solved but i dont know what caused it initially, never touched any files on server. Could be deleting packages from admin tab |
Description
i have a problem with a specific docker package in my instance. seems like some file or database corruption took place and this package cannot be pulled properly anymore. all other containers work.
i tried deleting all instance container packages using script multiple times, pushing new images to that container, it does not help.
first got this issue on version 1.17.1, updating to 1.17.3 did not help.
pulling image
meanwhile in gitea
can i somehow completely reset container packages in instance?
Gitea Version
1.17.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Debian 5.10.149-2 (2022-10-21) x86_64 GNU/Linux
How are you running Gitea?
locally compiled
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: