Open rofafor opened 5 years ago
This is a good suggestion, thanks. Currently we are using docker registry distribution directly, not build locally yet. But maybe we'll have to do this in future if we have much more important patches that Harbor extremely need and we can't wait too long.
IMO, the faulty S3 interface is used only during garbage collection in registryctl and the required binary is built from the docker registry distribution version control. Adding support for patches into this phase would be quite clean implementation: https://github.com/goharbor/harbor/blob/master/make/photon/registry/builder#L23 https://github.com/goharbor/harbor/blob/master/make/photon/registryctl/Dockerfile#L12
@rofafor Yes I know, but currently we didn't have a place to maintain the patch.
@reasonerjt has suggested to fork the docker & registry git repo, and maintain our own branch, but this still need some effort to think about how to organize the build process.
@xaleeks since it's merged to master
of upstream registry, we may consider to cherrypick and compile it to include the fix?
Shouldn't we directly use the newest upstream registry, not just cherrypick
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.
If you are reporting a problem, please make sure the following information are provided:
Expected behavior and actual behavior: Garbage collection fails when using Ceph as S3 storage:
This is due to a bug in Docker registry that's been finally fixed in the master branch: https://github.com/docker/distribution/pull/2879
I validated the fix by cloning the current docker/distribution master (79f6bcb), building the registry binary and replaced the one in the goharbor/harbor-registryctl-v1.8.1 image and finally the garbage collection is working fine.
I recommend that this small fix will be cherry-picked into Harbor's next release unless there aren't any newer registry releases than the current 2.7.1.
Steps to reproduce the problem:
Versions: Please specify the versions of following systems.