<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[[ProGet] Docker Feeds Self Connector &amp; Caching]]></title><description><![CDATA[<p dir="auto">Hi ,</p>
<p dir="auto">I have two Docker feeds configured as follows:</p>
<ul>
<li><strong>Feed A:</strong> Docker feed with connector caching enabled.</li>
<li><strong>Feed B:</strong> Docker feed containing local and remotely cached images.</li>
<li>Feed A uses a self-connector pointing to Feed B (<code>http://localhost/feedb/</code>).</li>
</ul>
<p dir="auto">When I try to pull an image from Feed B through Feed A with caching enabled, <strong>the Docker pull fails, repeatedly showing "Retrying" and eventually returning "unexpected EOF".</strong></p>
<p dir="auto">This happens with both local and remotely cached images in Feed B.<br />
This also causes images and layers to become corrupted on both feeds.</p>
<p dir="auto">In diagnostic center appears this :<br />
Screenshot 2026-09-25 alle 11.03.35<img src="/assets/uploads/files/1790327058982-a9a29e5e-a257-495c-931c-1c25b00479d3-image.jpeg" alt="a9a29e5e-a257-495c-931c-1c25b00479d3-image.jpeg" class=" img-fluid img-markdown" /></p>
<p dir="auto">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.</p>
<p dir="auto">I've reproduced this issue multiple times, including on a local ProGet instance without Apache or any reverse proxy.</p>
<p dir="auto"><strong>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?</strong></p>
<p dir="auto">Thanks!</p>
]]></description><link>https://forums.inedo.com/topic/5846/proget-docker-feeds-self-connector-caching</link><generator>RSS for Node</generator><lastBuildDate>Fri, 25 Sep 2026 22:25:57 GMT</lastBuildDate><atom:link href="https://forums.inedo.com/topic/5846.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 25 Sep 2026 09:05:51 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to [ProGet] Docker Feeds Self Connector &amp; Caching on Fri, 25 Sep 2026 10:46:16 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/atripp" aria-label="Profile: atripp">@<bdi>atripp</bdi></a> Hi Alana,</p>
<p dir="auto">Thanks for the clarification!</p>
]]></description><link>https://forums.inedo.com/post/20093</link><guid isPermaLink="true">https://forums.inedo.com/post/20093</guid><dc:creator><![CDATA[federico.conoscenti]]></dc:creator><pubDate>Fri, 25 Sep 2026 10:46:16 GMT</pubDate></item><item><title><![CDATA[Reply to [ProGet] Docker Feeds Self Connector &amp; Caching on Fri, 25 Sep 2026 10:26:07 GMT]]></title><description><![CDATA[<p dir="auto">Hi <a class="plugin-mentions-user plugin-mentions-a" href="/user/federico.conoscenti" aria-label="Profile: federico.conoscenti">@<bdi>federico.conoscenti</bdi></a> ,</p>
<p dir="auto">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.</p>
<p dir="auto">The Docker API specifies that the index is located at <code>/v2/_catalog</code>, and as you can see, there's no indication of "feed". For example: <a href="https://proget.inedo.com/v2/_catalog" rel="nofollow ugc">https://proget.inedo.com/v2/_catalog</a></p>
<p dir="auto">A "feed" is just the first portion of the repositories namespace.</p>
<p dir="auto">Thanks,<br />
Alana</p>
]]></description><link>https://forums.inedo.com/post/20092</link><guid isPermaLink="true">https://forums.inedo.com/post/20092</guid><dc:creator><![CDATA[atripp]]></dc:creator><pubDate>Fri, 25 Sep 2026 10:26:07 GMT</pubDate></item></channel></rss>