Hello Matt,

Is Web.BaseUrl set to https://host.name.net in https://host.name.net/administration/advanced-settings? Is there a reverse proxy between ProGet and the internet that requires authentication, or that might be modifying authentication headers?

If you access the /v2/ URL in your browser, there should be a header like WWW-Authenticate: Bearer realm="https://host.name.net/v2/_auth",service="host.name.net".

EDIT: We have updated our Docker documentation to include this information and more information about setting up your Docker client and ProGet server.

@aslepikas_5779 said in docker pull from proget not working:

@ben

I updated to 5.2.25 where PG-1669 was fixed. This still appears to be an issue, same warning as above, only difference is the User Agent field

User Agent: docker/19.03.3 go/go1.12.10 git-commit/a872fc2 kernel/4.4.0-165-generic os/linux arch/amd64 UpstreamClient(Docker-Client/19.03.3 \(linux\))

Is the stack trace actually empty? If not, it would be very helpful in tracking down this bug.

Hello @aslepikas_5779 and @jyip_5228:

It looks like this happens in the processing of the Authorization: Bearer anonymous header. I've filed PG-1669 to fix this.

Hello @jyip_5228,

Anonymous Docker feed access is supported, and a 500 response is (almost) always a bug.

In the ProGet advanced settings, you can set Diagnostics.FeedErrorLogging to the Docker feed's numeric ID and it should give more information about the failed request in the diagnostic center.

Hello @Adam,

What you are doing is correct; this is a bug in the Windows extension.

I've filed inedox-windows#76 to fix this.

Hello @tdean_3904,

This appears to be because the Docker extension doesn't create its own working directory automatically. To work around this, add the following operation call right before the Docker operation:

Ensure-Directory
(
    Name: $WorkingDirectory
);

Hello @PhilippeC,

Thanks for the repro case. I've filed this as OT-355.

@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.

Hello @James-McAllister_0459

For the API key, use HTTP basic auth with api as the username and the API key as the password. You can also obtain a token via the Docker auth flow, but that's much more complicated.

The manifest must be deleted by digest, not tag, so the URL should have /manifests/sha256: in it rather than just /manifests/ followed by a tag.

Hello @pcoombe_0297,

You can use api as the username and an API key as the password for any feed API supported by ProGet.

The auth format is HTTP Basic auth, so you'd prefix the API key with api: and then base64-encode the result.

You can also log in interactively via the npm login command. If your ProGet username cannot be used as an NPM username (such as a qualified domain user), ProGet will also accept the username via the email field.