Here are the features by edition: https://inedo.com/support/documentation/proget/administration/license ProGet Free is allowed for companies, however that edition only receives "community support" (i.e. this forum).

There was an issue (PG-1208) with semantic version-enabled NuGet feeds and retention policies fixed in v5.0.8 - an upgrade should resolve this.

Yes, that is OK, the differences for each edition are outlined here: https://inedo.com/support/documentation/proget/administration/license

Hi Ryan, Sorry for the delay in getting back to you - we're planning to add this to ProGet 5.2, which currently has a release date of April 11. It should be included in Inedo SDK 1.1.2 (see tentantive spec here). Does that look like it will cover your situation?

Thanks Alana, once I installed the certificate into my 'Trusted Root Certification Authorities' and restarted the docker daemon on my client machine, things are working nicely. Thanks again for your help!

Just to close this post: this was fixed in InedoCore 1.0.12, after diagnosing the issue on a ticket (EDO-5683).

As a followup, it's worth mentioning that this occurs specifically when directory providers are switched. The "Active Directory (New)" user directory requires the user@domain.tld format, so switching from the previous "LDAP & Active Directory" user directory (which supported netBIOSdomain\user) no longer can impersonate.

You got it working though :)

Hello Scott, This is done for 1-part repository names to match the behavior of Docker Hub. You should still be able to access the container without library/; that is, this should also work: <proget_server>:80/<container_feed>/<container_name>:<tag>

The groupName refers to the package's group name, and it's optional. A universal package is identified by group + name + version. The files do need to be artifacts; that's what will be zipped up and sent to ProGet.

After doing the steps in the links, I was able to remove and re-install proget (using offline installer). After that, Hub still didn't work, so I tried running the online-installer which downloads the Hub at the beginning of the install and that seemed to fix the Hub. Thanks for your help Dean.

Thank you for the report, this is resolved via: PG-1447

That's awesome, thanks!

Hello Eric, I think Docker requires at least one . in the hostname, and it's trying to access the default Docker hub. Another way that might work would be to add the port number to the hostname: <server name>:443/<feed name>/library/redis (the library part is optional to match the Docker hub, so <server name>:443/<feed name>/redis should also work)

Sorry on the delayed response; PG-1472 should fix the version selector failing for packages with partially missing snapshot metadata, like maven-archetype-plugin, which was used to test.

Unfortunately this was a regression present in 5.1.19, but has since been fixed in 5.1.20 which was released earlier today.

Upgrading to v5 seems to have fixed this

The Docker Client does not support integrated windows authentication; as a work-around, you'll want to set up a second ProGet site (different port or host name) in IIS that points to the existing folder but doesn't use integrated authentication.

Hello Ta, I was unable to find any mention of what metadata keys the Docker Hub looks for for those values, but I've filed PG-1443 to display all labels without any special formatting.