Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
ProGet GET requests not returning expected payload
-
GET requests on https://our.proget.com/v2/qa-feed-1/library/nginx/manifest/latest with header Accept: application/vnd.docker.distribution.manifest.v1+json return a payload of type application/vnd.docker.distribution.manifest.v2+json which doesn’t contain the data we are expecting (i.e. we can’t explore the layers of the manifest through the requested version of this manifest).
See screenshot:
Note: Regarding requested URL: /api/registries/1 – part of the URL is only a backend proxy, passing the request as-is to the Proget API – basically transforming http://localhost:9000/api/registries/1/v2/… to https://our.proget.com/v2/…
This issue was mentioned on forum topic 3541, but we thought it best to just log as a separate topic.
-
I'm not really sure I totally understand the issue, or how to resolve it... but I'll explain how a
GET manifestrequest to your URL would work.Basically, ProGet returns whatever manifest file you uploaded, or whatever was downloaded via the connector. We do not generate the manifest files, or pay attention to the
Acceptrequest header.I understand that
application/vnd.docker.distribution.manifest.list.v2+jsonis a "fat manifest", which is basically a manifest that points to other manifests on different architectures. So you don't know exactly what image you'll get until you install it on the machine.So if you want to inspect layers, you would first need to decide which manifest to use, I guess
Cheers,
Alana
