Harbor doesn't support pull cache as a mirror registry

[int32bit]

We use harbor as our private registry, but it seems that harbor has not supported pull cache yet. If I pull an image which doesn't exist in the harbor, the image can't be cached
automatically. To configure a registry to run as a pull through cache, the addition of a proxy section is required to the config file(config.yml),see https://github.com/docker/distribution/blob/master/docs/mirror.md

[hainingzhang]

When enabling the mirror pulling features, the registry's original push/pull does not work any more. So that's why Harbor does not support mirror for now. We may consider a feature to support mirror in the future.

[int32bit]

The registry's original push/pull does not work any more, we have not test it yet. If it's true,I think it can be configured as option. @hainingzhang

[hainingzhang]

yes, it could be a feature that the registry serves as a mirror only, not a "normal" registry. We will consider to put this in our roadmap.

[int32bit]

We don't understand why the registry's original push/pull does not work any more if enabling the mirror pulling features. In fact, I modify the harbor/Deploy/config/registry/config.yml manually and append proxy to enable pull cache according to official documents, it works fine！We can pull/push as a normal registry too. @hainingzhang

[chovy-3012]

yes,if modifying the harbor/Deploy/config/registry/config.yml manually and append proxy,it can pull cache from docker-hub,but i can't push my image to pivate registry

[tyhoho]

same scenario with @vergilchiu, it can sucessfully pulling images and caching, but fails with pushing images to private registry
Anybody is looking into this issue?

[reasonerjt]

I believe this is a limitation in docker registry, see #220

[tyhoho]

@reasonerjt Thanks! This helps a lot! I've been searching this issue a while.