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!

How to configure Docker Connectors



  • I am trying to setup a test instance of ProGet. I have a Nuget connector for my Nuget Feed which seems to work fine. I am now trying to do the same thing for my Docker feed. I have configured both Docker Hub and Microsoft connectors (which seem to be healthy). But I don't seem to be able to pull any images from my private repository with those connectors attached.

    docker pull http://{my-proget-domain}:{my-proget-port}/{docker-feed-name}/mcr.microsoft.com/mssql/server:2019-latest
    docker pull http://{my-proget-domain}:{my-proget-port}/{docker-feed-name}/mssql/server:2019-latest
    docker pull http://{my-proget-domain}:{my-proget-port}/{docker-feed-name}/mcr.microsoft.com/mssql/server
    docker pull http://{my-proget-domain}:{my-proget-port}/{docker-feed-name}/mssql/server
    

    These all return: "invalid reference format"

    What am I doing wrong?

    There doesn't seem to be any good documentation on this. It would be really useful if the documentation actually had some examples of usage with screenshots.


  • inedo-engineer

    Hello @izzy95453_1154,

    I completely understand you frustration here and I will bring these comments up with the documentation team. I believe the documentation you are looking for exists in our private container registry documentation, but I will summarize it below.

    Looking at your commands, I can definitely help you with this. The first thing you will need to do, is setup a private container registry. The Docker client by default requires SSL. Looking at your commands, you are currently using an HTTP protocol. This will require you to setup an insecure registry.

    If you are requiring authentication, you then need to login to your registry. You can log in either with a username and password or you can generate an API Key and use api as the username and the key as your password. You can do that with the following command:

    docker login {my-proget-domain}:{my-proget-port}
    

    Once you have setup your insecure registry and logged in (if not using anonymous access) then you should be ready to pull your image. To pull the image above, the command syntax would be:

    docker pull {my-proget-domain}:{my-proget-port}/{docker-feed-name}/mssql/server:2019-latest
    

    The reason you are getting the syntax error above is because you are specifying http://. Docker requires just the server and port. I also want to point out that the Docker client requires a . in your domain name or :{port} to exist in the first url section. That is what the Docker CLI uses to identify this is a private registry and not Docker Hub. For example:

    • ProGet URL: http://proget-server using the standard HTTP port 80, Docker URL proget-server:80\{feed-name}\{image}:{tag}
    • ProGet URL: http://proget.localhost using the standard HTTP port 80, Docker URL: proget.localhost\{feed-name}\{image}:{tag}
    • ProGet URL: http://proget-server:2365, Docker URL: proget-server:2365\{feed-name}\{image}:{tag}

    In ProGet 6, we will be adding Feed usage instructions that should help guide users going forward. ProGet 6 will be released later this year.

    Hope this helps!

    ~ Dan



  • Hi @Dan_Woolf ,

    Thanks for all that information.
    I believe I have setup a "private container registry"

    However, I am now getting:

    Error response from daemon: manifest for {my-proget-domain}:{my-proget-port}/{docker-feed-name}/mssql/server:2019-latest not found: manifest unknown: manifest unknown
    

    I am also using the docker version of proget for my testing, so not sure if I can setup with an SSL certificate there?

    Regards,
    Izzy


  • inedo-engineer

    Hi @izzy95453_1154,

    I think the next step is to verify that your connector is configured correctly. Can you search in the ProGet UI for mssql/server? That should return the remote image for SQL Server. If you then click on the the Remote Tags tab and then click on 2019-latest, you should see the command syntax for pulling that image. Can you please verify that matches what you are using?

    ~ Dan


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation