Octopus + ProGet + Docker = Not Working?

Legacy Infrastructure
1

Hi Guys,

We are using Octopus 3.13.10 and we are trying to integrate it with ProGet for Docker, with no success (Library -> External Feeds), and I was wondering if anyone here had this issue our similar difficulties.

The Octopus-ProGet integration for NuGet it’s working perfectly using this address: “https://proget-server/nuget/repo-name/”. However, the integration for Docker gives an Empty List (not an error message).

For what I understood, you only need to specify the main endpoint (“https://proget-server/”). Since the same user is used on both integrations and has access to the required repos, but still, empty list.

Did anyone experience this issue before? It’s a known problem? Are we missing something?

I appreciate any help or advice. Thanks in advance!

2

Hi Domenico,

Thanks for getting in touch! Currently this is due to ProGet not implementing the _catalog endpoint. We have a bit of a mention of this on our Docker registries documentation page:

Note that as of the current version of ProGet (version 4.6.7 (Build 2)), their Docker Registry Feed does not expose the full Docker API and is missing the _catalog endpoint which is required to list the available packages for release selection. It has been indicated that this may change in a future release.

Unfortunately I was unable to find an ETA of any kind of fix, nor was I able to find a workaround here. Sorry for the lack of help!

Let me know if you have any further questions here.

Best regards,
Daniel