Proxy Cache (Pull Through)

[flyingfishflash]

Perhaps I'm misunderstanding the purpose of the proxy cache -

I have a docker hub registry configured with my credentials and the connection tests successfully.
I have a corresponding proxy-cache project created.

Using podman:

# a couple of days ago, gitea:latest is v1.18.1
podman pull registry.xxx.tld/proxy-docker.io/gitea/gitea:latest

The repository was properly created in the project and available for pulling.

# today, gitea:latest has been updated to v1.18.2
podman pull registry.xxx.tld/proxy-docker.io/gitea/gitea:latest

Yet harbor is only returning the cached v1.18.1 latest tag.

My understanding from the documentation is that harbor should be polling docker hub via HEAD request first to see if the tag has been updated, and then updating the cache and returning to the original client requester the most recent tag available upstream.

Is this incorrect? Maybe I've misunderstood. Using harbor v2.7.0

EDIT: Interestingly running the same with docker instead of podman works partly. It triggers the request to upstream docker hub, and the most recent manifest for latest tag is added to the harbor proxy/repository and returned back to the client. However it doesn't tag the newest image with 'latest', the originally cached image retained the 'latest' tag.

Perhaps it's something to do with my podman configuration.

[flyingfishflash]

In the end I just used scheduled replications and pointed all my containers to the replicated images in the custom namespace. This is working fine.