Does registry mirror mode support GET manifest caching for OCI images?

[jpmmota]

We are running Dragonfly via the official Helm chart (dragonflyoss/helm-charts) in registry mirror mode with containerd. We'd like to know whether the dfdaemon registry mirror is intended to handle GET manifest requests (GET /v2/<name>/manifests/<reference>) in addition to blob downloads, and if so, what configuration is required.

Environment

• Deployment: Kubernetes, Helm chart from dragonflyoss/helm-charts (chart version 1.6.13)
• Runtime: containerd, configured to use Dragonfly as mirror

What we tried

• registryMirror with dynamic: true – No improvement; we also found that the v2.4.0 dfdaemon config docs do not list a dynamic field under proxy.registryMirror.
• registryMirror without dynamic – Using only documented fields (addr, enableTaskIDBasedBlobDigest). GET manifest still did not work as expected (we expect either mirror to serve/cache manifest or to proxy it correctly).
• Adding proxy rules for manifests – We added a rule so that manifest URLs are matched (e.g. manifests/.* or manifests/sha256.) in addition to the default blobs/sha256.. GET manifest still did not work.

Questions

1. Is GET manifest (/v2/<name>/manifests/<reference>) supported in registry mirror mode (caching and/or proxying)? This would be helpful when the origin repository is unavailable.
2. If yes, what is the required configuration?

Thanks for maintaining Dragonfly!

[imeoer]

@EvanCley @imeoer