Hello Neil,

When I download that package from the PowerShell gallery, it has the version number 12.2.0 (not 12.2.0.0 as is shown in the UI).

I'm not sure where the extra .0 is coming from.

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)

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>

Hello Philippe,

I've filed this as OT-283.

Hello Ryan,

Sorry about the delayed response.

The Push to ProGet Visual Studio extension is for Universal (upack) feeds, not NuGet (nupkg) feeds.

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.

Hello Martin,

I've filed PG-1422 to stop ProGet from checking whether anonymous users have any feeds they can access. You may also want to check in SSMS whether any of the indexes need to be rebuilt or reorganized.

Hello Adam,

I've filed PG-1409 to allow setting a password on a connector with a blank username, which will allow bearer tokens to be used in npm.

Hello Philippe,

If the example code is identical to what you're running, the 10GB is misspelled as 1OGB (with the letter O instead of a zero).

Hello Jon,

I've released version 1.0.2 of the Jenkins plugin to fix the build never being found, and it appears to work properly with importing assets as well.

Hello Jon,

project/job/jobname should still work.

It appears that the code to wait for a build to finish is getting stuck:

Queueing build in Jenkins...
Creating HttpClient with username ben...
Retrieving CSRF protection header value...
Posting to http://jenkins:8080/job/project/job/jobs/build...
Jenkins build queued successfully.
Queue item number: 1
Creating HttpClient with username ben...
Retrieving CSRF protection header value...
Waiting for build to start... (In the quiet period. Expires in 2.8 sec)
Creating HttpClient with username ben...
Retrieving CSRF protection header value...
Waiting for build to start... (In the quiet period. Expires in 0.62 sec)
Creating HttpClient with username ben...
Retrieving CSRF protection header value...
Waiting for build to start... (???)
Creating HttpClient with username ben...
Retrieving CSRF protection header value...
Creating HttpClient with username ben...
Retrieving CSRF protection header value...
Waiting for build to start... ()
Creating HttpClient with username ben...
Retrieving CSRF protection header value...
Creating HttpClient with username ben...
Retrieving CSRF protection header value...

I'll try to find the root cause of this.

Hello Jeremy,

It seems that the Maven feed code in ProGet is incorrectly identifying all prerelease Maven package versions as snapshot versions.

I've filed this as PG-1380.

Hello Michael,

Does the feed have a connector for https://www.powershellgallery.com/api/v2? You can check the connectors attached to a feed from the Manage Feed page.

If the PowerShellGet package was cached from a connector and the connector was subsequently deleted or disconnected from the feed, the package will still show that icon.

Hello Boubacar,

There have been a lot of changes to Docker feeds in ProGet 5.1. Does pushing the Windows image work on a newer version of ProGet?

Hello Antoine and Anton,

I've filed this as PG-1376.

Hello Florian and Antoine,

I've filed this as PG-1376.

Hello Jan,

I've filed PG-1350 to improve the error message when no connector successfully returns a manifest.

Hello all,

ProGet 5.1.7 fixes an additional issue that was causing SemVer2 NuGet packages to fail to download: PG-1329

Update: I've filed this bug with Docker: https://github.com/docker/distribution/issues/2649

When I view the data being sent between ProGet and the Docker client, there's a HEAD request that would normally return this body:

{"errors":[{"code":"UNKNOWN","message":"Could not resolve ProGet feed \"docker\". Docker repository names in ProGet must include the feed as a prefix. Example: MyFeed/library/ubuntu","detail":[]}]}

However, because it's a HEAD request, Docker doesn't receive any body.