Posts made by Dan_Woolf

Hi @bryan-ellis_2367,

What version of ProGet are you using?

I would also clear your cookies in your browser. It is most likely trying to use your previous login information still. One way to test this is to open a private browsing tab in your browser and see if you still have the same error.

Thanks,
Dan

Hi @mcascone,

The package deployment API will show in the History tab of the package. The Package usage block is actually part of Package Usage Scanners that are only supported on specific feed types. Which feed type are you using in this situation?

Thanks,
Dan

Hi @Fauzi-Ashurex_3595,

I see you have submitted a formal support ticket for this. I will post back the final solution to this post once it is fixed.

Thanks,
Dan

Hi @shiv03_9800,

No problem! Glad I can help!

Please let me know after Otter 3.0.11 is released if that fixes the PowerShell agent for you.

Thanks,
Dan

Hi @shiv03_9800,

Thank you for confirming that for me.

I was able to find a regression issue in the PowerShell Agentless Server configuration, OT-427. Our engineers were able to patch the issue and it will be released on Friday September 24 in Otter 3.0.11.

The setup instructions are pretty straight forward for setting up these servers. I have included the basics below. The key thing is to make sure to set the Temp Path on the servers.

For an SSH server:

1. Create a Secured Credential for the SSH credential
2. Create the server (make sure to set the temp path)
   • The temp path must exist on the remote server and the SSH user must have read/write/delete access to that folder

For a PowerShell server (Otter 3.0.11+):

1. Create a Username Password Secured Credential (Integrated Authentication will not work in Docker)
2. Create the server (make sure to set the temp path)
   • The temp path must exist on the remote server and the user must have read/write/delete access to that folder

Hope this helps!

Thanks,
Dan

Hi @shiv03_9800,

Thanks for sending this over to us. Just to clarify, you are to setup a PowerShell and an SSH based agentless servers and you are getting the listed errors and you are looking for how to set these up. Is that correct?

Thanks,
Dan

Hi @scusson_9923 ,

Thanks for sending the updated info. Would you be able to attach to output of the Clair container (docker attach <RUNNING_CLAIR_CONTAINER_NAME>) and run the vulnerability downloader from ProGet? Clair will output the exact HTTP error that is happening when connecting to ProGet. That will help to confirm if it is an SSL issue or not.

One other thing to try would be to upgrade Clair to 2.1.7. I know they fixed an issue relating to a RHEL feature they use, that happened to be affecting my test environment.

Sorry for the delay on our end. Clair has released a new version and API which makes finding the older documentation a bit harder. We have not tested it with the latest version of Clair (4.2.2), but I would expect their to be some API issues. We are waiting for Clair's development to stabilize a bit more before we implement the new API. Last time we tested it, Clair's v4 API had so many bugs that it prevented us from supporting it.

Thanks,
Dan

Hi @scusson_9923 ,

Can you please confirm that you do not see any errors in the diagnostic center after running a vulnerability scan? I just want to confirm that this is an SSL problem and not an underlying ProGet issue.

Thanks,
Dan

Hi @kichikawa_2913,

NuGet will always use a .nugetv2 folder under the packages root path, unless you customize it at the Feed level. If you change the Storage.PackageRootPath, it will change the location of the .nugetv2 folder. I will note though, if you change the Storage.PAckageRootPath, it will also update any other feed type path that has not already been changed. Currently the only way you can customize the NuGet storage path is at the Feed level.

Thanks,
Dan

Hi @antony-booth_1029 ,

I'm having trouble recreating this issue. Do you have Deployables configured with the different configuration environments? Also do you see the correct environment selected when you look at each configuration instance's settings?

Thanks,
Dan

Hi @mjc_4927,

Can you please let me know what version of BuildMaster you are running?

Your tasks look to be configured correctly. Let me chat with our engineering team and I'll let you know what I find out!

Thanks,
Dan

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

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