Proxy Cache

[antwacky]

I hate to reference this issue once again, but I'm not sure how to proceed.

The issue mentions that the docker client, on pull, converts the tag to a SHA and prevents harbor from being able to cache the image with a tag.

This behaviour means that we are hitting the dockerhub rate limit on a regular basis - how do I move past this? Can Harbor not match the SHA with the cached SHA image?

[antwacky]

I tried adding my credentials to the registry configured for the proxy cache but it doesn't seem to be using them.

I'm getting the rate limit error from Docker, although I can see that my account has 197 pulls remaining. I expect the proxy cache to be using my authenticated account when pulling from Dockerhub?

[antwacky]

Sorted it, it was nothing to do with the proxy. Rather I didn't realise that docker buildx required seperate configuration to configure it to use the proxy.