[ProGet] Docker Feeds Self Connector & Caching

[federico.conoscenti]

Hi ,

I have two Docker feeds configured as follows:

• Feed A: Docker feed with connector caching enabled.
• Feed B: Docker feed containing local and remotely cached images.
• Feed A uses a self-connector pointing to Feed B (http://localhost/feedb/).

When I try to pull an image from Feed B through Feed A with caching enabled, the Docker pull fails, repeatedly showing "Retrying" and eventually returning "unexpected EOF".

This happens with both local and remotely cached images in Feed B.
This also causes images and layers to become corrupted on both feeds.

In diagnostic center appears this :
Screenshot 2026-09-25 alle 11.03.35

The only workaround I've found is to disable caching on Feed A and reindex both feeds, enabling the options to remove images with corrupted or missing layers, which unfortunately results in data loss. After that, everything works correctly.

I've reproduced this issue multiple times, including on a local ProGet instance without Apache or any reverse proxy.

Is this a known issue or a bug? Is disabling caching the correct workaround, and is using a self-connector with this URL the correct configuration?

Thanks!

[atripp]

Hi @federico.conoscenti ,

Self-connectors won't work in Docker as repositories are already rooted and accessible across all feeds. It's just a quirk of the Docker API really.

The Docker API specifies that the index is located at /v2/_catalog, and as you can see, there's no indication of "feed". For example: https://proget.inedo.com/v2/_catalog

A "feed" is just the first portion of the repositories namespace.

Thanks,
Alana

[federico.conoscenti]

@atripp Hi Alana,

Thanks for the clarification!