Perfect solution! Thanks!

k, we're good. Upgraded successfully!

I'm afraid I can't reproduce this :( Using the latest ProGet version, I created a PyPi feed, added a connector to Pypi.org, then browsed, downloaded, and pulled the package.

This is to be expected; unfortunately the Docker Hub does not support searching via API, thus ProGet can't possibly search containers. But you can still get to the container by entering in the name directly in the URL.

The 504 error indicates that the dotnet client on your linux server isn't able to connect to ProGet, or that there's some intermediate proxy's preventing the request. So, I would investigate the networking side of things. Note that the password setting (CleartextPassword vs EncryptedPassword) doesn't matter, since they both arrive to ProGet as the same Basic authentication header.

@atripp said in Proget is not responding frequently: e to set your Service to Auto-recover. For bad database connectivity, that's the best solution. Thanks! The service is still running when it happens.. And I dont see any errors about DB connectivity on event logs.

Good news ...

@atripp Thanks for the update. We do need this fixed but for now we have a work around.

I realized I could use maven feed in ProGet for ivy as well. As far as using ivy instead of maven, we use Ivy as purely dependency management tool with ant.

Great news, Alana! Thanks.

@atripp @ben I can confirm that it works! No more warning when doing apt update and I can successfully search for packages now. Thanks again!

Thank you Pb is gone with 2.2.10 Best regards

Thanks for the detailed information, that's very interesting and a great assessment. We wouldn't have found this using all of these variables, especially the different Windows desktop version I suspect this might be a bug in the underlying libraries? We just use an HttpListener and a HttpWorkerRequest, both which should handle all of this, in the simplest way possible. I'll ask around and see if anyone knows. But I guess, at least you found a work-around which I'm glad to hear!

Your best bet would be to use the helm api endpoint; we don't document how third party apis work (it's hard enough to document our own!), but you could use a tool like fiddler to see what the helm client uses.

I know it's a little late. I had the same problem today and solved it by installing Microsoft Sysinternals SubInCal (https://www.microsoft.com/en-us/download/details.aspx?id=23510). Set the permissions with: cd "C:\Program Files (x86)\Windows Resource Kits\Tools\)" subinacl.exe /service INEDOBMSVC /grant=domain\user=PTOS

Thanks for this post id did help me a lot. I did also get the message "Specified from feed '' does not exist." while trying package promotion. This message is missleading as the real issue was the http Client not passing all the content types as the server wanted. I did try with postman and powershell Invoke-WebRequest. Think the server is unecessary strict with handling the requests, but maybe there is a reason for that. Please consider adding a few "HttpClient" example to the documentation in different languages like powershell, java,c#. It would save the customer a lot of time. https://docs.inedo.com/docs/proget/reference/api/package-promotion

@atripp Thanks for the reply. I submitted a Pull Request myself to the dependabot-core repo.

Hello; What are you trying to do? This definitely won't work for several reasons. Ensure-File is an "Ensure" operation and will detect configuration drift and can optionally create the file if it doesn't exist; but in this case, it would be a 0-byte file named test.zip, which isn't a valid zip Extract-ZipFile is a "Execute-only" operation, which means it will run only within a block (e.g. { ... } ) if drift was detected (i.e. the file didn't exist in the operation before); but if that was the case, it would fail because it's not a valid zip file You probably want to use an Orchestration plan for this. Please read through this eBook to get feeling for how configuration and Orchestration Plans: https://inedo.com/support/resources/ebooks/windows-first-iac-cca

Thank you. We have upgraded and now it works. For clarity any REST API call would not work before the upgrade.

@James-McAllister_0459 said in deleting docker images via REST API: Is there any way to get the published date or created date of the image from a REST api? The Docker API in ProGet doesn't (currently) return a Last-Modified header, but depending on which date you want, it can still be accessed: Published date can be accessed via the native API using the tables you identified. However, this API is generated directly from internal ProGet database procedures, so this may break in the (unlikely) event that ProGet's Docker database structure changes. Created date is a property of the image, which is embedded in the manifest's config field. Inside the JSON blob referenced by the manifest, the creation date of the image is in a field named created. This is optional in the Docker specification, but if you're building your own images, it should always be present.