Proget as Docker Feed

[cgambino]

We are trying to get Proget (Version 5.2.27 (Build 6)) to act as a docker feed, and are getting the following error:

Unhandled error on request: https://deploy.XXXX.com/api/Spaces-1/feeds/Feeds-1001/packages/search?term=&take=11&skip=0 c49626aa967b4f5c9354de1ec4d75774 by : One or more errors occurred. Octopus.Core.Packages.Docker.DockerOAuthException: Request to https://proget.XXXX.com/v2/_catalog failed with InternalServerError:Internal Server Error.
at Octopus.Core.Packages.Docker.DockerRegistryOAuthClient.d__3.MoveNext() in C:\buildAgent\work\abb2fbfce959a439\source\Octopus.Core\Packages\Docker\DockerRegistryOAuthClient.cs:line 74
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Octopus.Core.Packages.Docker.DockerRegistryOAuthClient.d__2.MoveNext() in C:\buildAgent\work\abb2fbfce959a439\source\Octopus.Core\Packages\Docker\DockerRegistryOAuthClient.cs:line 43

[Justin_Walsh]

Hi @cgambino

Thanks for reaching out - The ProGet Docker feed is not one that we explicitly tested against however if it conforms the the docker api specifications it should in theory work fine. I know we did have issues in earlier versions of Proget not correctly implementing the whole API spec, as noted here: https://octopus.com/docs/packaging-applications/package-repositories/docker-registries#DockerRegistriesasFeeds-OtherOptions - I’m not sure if they’ve fixed this in 5.2.27.

The next place I’d check here is the server logs on the proget server, as that 500 error is being thrown from there, so it may be another auth-related configuration if the previous issues have been resolved.

I hope this helps!