Ramkumar Chinchani
Ramkumar Chinchani
Pls close this issue if the issue is resolved.
@wuhuizuo we don't have this behavior currently. This should be a feature request.
Do we need a predictable timeout for the HEAD request and then error handling for that?
Should pair with https://github.com/project-zot/zot/pull/2968
@ieugen just so we are clear, is this a documentation issue? or a functionality regression? If the former, we are still updating docs.
| To confirm this is related to the image trust extension, I would remove this section from your configuration and try again. @ieugen did this ^ work for you?
@NetAppBlueDevil are you using the minimal or the full image? Could you try with the latest release? https://github.com/project-zot/zot/blob/main/examples/config-sync.json
@aritas1 Firstly, thanks for filing all the issues you are finding. "**Some clients** will test on /v2/" ^ not all clients are going to be supported and `zot` is **not**...
@joshbwlng so basically this is broken? https://www.rfc-editor.org/rfc/rfc9110.html#section-14.1.1-7 just curious why podman is referring to the blob from the end.
@joshbwlng pls do give us a PR, but fair warning that you may have to be a little patient with our ci wrt tests etc.