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

Garbage Collection #103

Open
Vertiwell opened this issue Apr 24, 2023 · 2 comments
Open

Garbage Collection #103

Vertiwell opened this issue Apr 24, 2023 · 2 comments

Comments

@Vertiwell
Copy link

Hi,
I'm getting this error with garbage collection:
failed to garbage collect: failed to mark: filesystem: Path not found: /docker/registry/v2/repositories
It was working fine for ages, maybe an update or something...
I've just enabled it via the helm chart.

@repcsi
Copy link

repcsi commented Sep 14, 2023

Hi @Vertiwell ,
I've seen a similar issue here:
distribution/distribution#3200

tldr workaround:
After I put an empty dummy object named empty into the /docker/registry/v2/repositories of the s3 server (Linode object storage in my case) garbage collection finished successfully.

Can you check it?

@Vertiwell
Copy link
Author

Hey repcsi, appreciate the response, I have added the empty file, mucked around with a few other things and no change, I continue to have the job fail.
I am now full s3, with images saving to my s3 target no issues, everything works great, just leaving garbage collection disabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants