Posts made by pariv_0352

I have installed 25.0.10 release. I can't reproduce the error anymore.

@stevedennis
I’ll try it as soon as it’s out :)

@atripp said in proget 500 Internal server error when pushing to a proget docker feed:

the code is not fixed in 25.0.9

Yes, I got it, just to clarify that I still have the error, so you can use me as tester )

Should I try 25.0.10-ci.5+ or wait for release?

I updated to 25.0.9 as well, and still have the issue.

I was about to start a new thread, but this one might be related to my issue. I can't push a Docker image to ProGet (version 25.0.8). Docker keeps retrying, but without success. The Diagnostic Center shows no errors. In the logs, I see:

A 500 error occurred in docker_feed: Nullable object must have a value.

info: Microsoft.AspNetCore.Hosting.Diagnostics[2]

      Request finished HTTP/1.1 PUT http://mydomain.com/v2/docker_feed/my_service/blobs/uploads/1f3bb6af-6666-497e-bb8e-6b621d584b9c?digest=sha256%3Addfc8032fb97dfcf37359445fcb93b9742fcdf6f5bfdd288081557bf461edac6 - 500 1091 application/json 10.8169ms

Then I tried 25.0.9-ci.14, same result.

vcpkg is a package manager developed by Microsoft. It's similar to Conan but can be easily integrated with Visual Studio after installation. It also offers very simple integration with CMake, making it easy to manage C++ libraries. Also it is more simple than Conan.

Hello, is there are plans to create vcpkg packages feed support?

I use Version 2023.9. And yes, I saw that thread, but looks like it is a bit different.

I run proget behind reverse-proxy. And that proxy sits on non-standard port.
And all works fine, but when I'm trying to access feed through browser it fails with Server Error 500: Invalid URI: The hostname could not be parsed.

If I run proget on non-standard port without reverse-proxy feed access works.
Looks like when proxy sets header X-Forwarded-Host to something with explicit port, it fails.
e.g. www.testdomain.com:82.

I found out that X-Forwarded-Host header is not very well defined in the case of ports. But I think proget shouldn't throw exceptions in this scenario and show feed page.

There is a workaround to set Web.BaseUrl, but its not suitable for me, because port may change over time. And I dont want to change Web.BaseUrl every time it changes.

Hello, I'm trying to install/download/pull to proget package HarfBuzzSharp.NativeAssets.Linux 2.8.2.1-preview.79, but it fails with error Invalid package version was specified.

For test purposes I created clean install of proget to other pc using docker.
Created one feed proxy with connector to docker hub with url https://registry.hub.docker.com

Tried to search for mongo in web interface - no results
Then I tried to run docker pull {proget_url}/proxy/library/mongo:5.0
docker response is Error response from daemon: manifest for {proget_url}/proxy/library/mongo:5.0 not found: manifest unknown: manifest unknown

docker container logs:

proget   | info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
proget   |       Request starting HTTP/1.1 GET http://{proget_url}/v2/_auth?scope=repository:proxy/mongo:pull&service={proget_url} - -
proget   | info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
proget   |       Request finished HTTP/1.1 GET http://{proget_url}/v2/_auth?scope=repository:proxy/mongo:pull&service={proget_url} - - - 200 21 application/json 0.4792ms
proget   | info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
proget   |       Request starting HTTP/1.1 HEAD http://{proget_url}/v2/proxy/mongo/manifests/5.0 - -
proget   | Running Drop Path Monitor...
proget   | Running Drop Path Monitor...
proget   | Getting list of feeds with a drop path...
proget   | Getting list of feeds with a drop path...
proget   | No feeds with a drop path.
proget   | No feeds with a drop path.
proget   | Drop Path Monitor completed.
proget   | Drop Path Monitor completed.
proget   | Running Execution Dispatcher...
proget   | Running Execution Dispatcher...
proget   | Checking for executions to dispatch...
proget   | Checking for executions to dispatch...
proget   | Execution Dispatcher completed.
proget   | Execution Dispatcher completed.
proget   | info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
proget   |       Request finished HTTP/1.1 HEAD http://{proget_url}/v2/proxy/mongo/manifests/5.0 - - - 404 81 application/json 8167.3262ms
proget   | info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
proget   |       Request starting HTTP/1.1 GET http://{proget_url}/v2/proxy/mongo/manifests/5.0 - -
proget   | info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
proget   |       Request finished HTTP/1.1 GET http://{proget_url}/v2/proxy/mongo/manifests/5.0 - - - 404 81 application/json 1993.6862ms

After that request I can search for mongo in web interface and there will be result with that name. And I can retrieve all remote tags for that image. But that's all I can do with it.

I thought that may be something wrong with our network, but this clean install I created on different network and provider.

1. I use 2022.1 version of proget.
2. I noticed it just before upgrading proget to a new version, because I use proget to retrieve new image versions of proget )
   But I was hoping that after upgrade all will work like always, so I got proget image direct from inedo repository
3. Docker Hub connector URL is https://registry.hub.docker.com
4. No it still fails with library and without with same response.

I have multiple other connectors to other public registries, and all of them stopped to work like this.

I have a feed with remote connector to docker hub. It was working ok for a long time. But recently I discovered that I can't pull new published images from docker hub through connector.
If I delete cached images, and execute, for example, docker pull our_proget_url/feed_name/mongo:5.0
then answer will be Error response from daemon: manifest for our_proget_url/feed_name/mongo:5.0 not found: manifest unknown: manifest unknown.
I even can search for that image in proget web interface and load and see all remote tags, but can't pull it.

Thank you, @rhessinger, for clarification.

Yes, I use common blob storage, and all that makes sense now.

Hi @atripp.

Looks like I misundestood logic of "FeedCleanup" job. Every time I run that job, it always says that Found 0 unreferenced blobs. and does nothing.
But "DockerGarbageCollection" job (which I didn't notice before you said about it) really cleaned storage from unused blobs.

What for FeedCleanup job then? I checked logs, it never found anything unreferenced.

I face the same problem (probably).
Even if I delete all images that use blob, it won't delete blob from disk during feed cleanup.
I checked digest in [DockerBlobs_Usage] - no entries, parsed [DockerImages].[ManifestJson_Bytes] for that digest - no entries.
It exists only in [DockerBlobs] and if i try to look for it in any other tables which I can join via [DockerBlobs].[DockerBlob_Id] - failed to find any records.

And that's not only one blob, looks like all unused blobs never deleted from storage.
I use windows images, they are huge, so I want to reclaim space from deleted images.

I use proget 6.0.10