docker-registry.helm
docker-registry.helm copied to clipboard
Garbage Collection
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.
Hi @Vertiwell , I've seen a similar issue here: https://github.com/distribution/distribution/issues/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?
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.