Hi @informatique_1703,

Does this happen for all images or just the one image? Do you see any errors in the console from docker?

Thanks,
Rich

Hi @informatique_1703,

Is this the error from ProGet or from the Docker client. Do you see any other errors in the ProGet diagnostics center when you try to push an image?

Thanks,
Rich

Hi @viceice,

Thanks for confirming that for me. I ran into a few issues on my test server with SQL 2014 and TLS1.2 support. You may want to make sure that TLS 1.2 is enabled on that VM. SQL Server 2014 and Windows Server 2012 R2 both had some unique issues with teh TLS 1.2 conversion (both needing updates to be able to enable them) . Although this did not cause an issue with hanging, it did cause my authentication to fail. You may want to check that.

Thanks,
Rich

Hi Phillipe,

I created an issue on GitHub, #8, to track adding this to the extension. I'll reply back once there is a CI version released of the extension.

Thanks,
Rich

Hi @viceice,

I'm having trouble recreating this issue. I tested this by setting up a SQL Server 2014 instance with updates installed to bring it to version 12.0.6372.1. I have tried both the proget and the progetmono images at version 5.3.12. Both of them boot up and run all the scripts completely fine. I have even tested using your exact docker command and only changing out the SQL connection string. So far I cannot get it to hang. Is there anything else unique about your network configuration? Do you have just a standard install of SQL Server? Is there any proxy or VPN that requests are routed through to connect to your SQL Server?

Thanks,
Rich

Hi @p-bruch_5023,

Thanks for bringing this to our attention. I have created a ticket, PG-1838, to track a fix for this. It will be realeased this Friday as part of ProGet 5.3.13.

Thanks,
Rich

Hi @nuno-guerreiro-rosa_9280,

The .NET Core version is definitely more effecient than the mono version. One of the biggest issues with mono is how it manages web requests. Mono reimplemented its web client and connection pool from scratch due to the complexity and internal dependencies of the .NET Framework. This is probably part of the reason you see the mono version tax the server a bit. As for NuGet querying all 40 packages in ProGet, we don't have much control over that. NuGet queries all sources in the list until it finds one. It will do custom sources first then fallback to NuGet.org last. There is an interesting ticket on NuGet's GitHub page discussing the priority (https://github.com/NuGet/Home/issues/3676).

Thanks,
Rich

Hi @nuno-guerreiro-rosa_9280,

I was finally able to recreate the issue. We created a ticket, ILIB-98, to track the issue. It will be released on Friday with ProGet 5.3.13.

Thanks,
Rich

Hi @nuno-guerreiro-rosa_9280,

No problem! Gald it helped!

Thanks,
Rich

Hi @nuno-guerreiro-rosa_9280,

You can reduce the logging by adding some environment variable parameters to your docker start command. The environment variable paramters you will need to add are:

-e 'Logging__LogLevel__Default=Warning'
-e 'Logging__LogLevel__Microsoft=Warning'
-e 'Logging__LogLevel__Microsoft.Hosting.Lifetime=Warning'

You can also set them to Error if oyu wnt even less logging.

Thanks,
Rich

Hi @nuno-guerreiro-rosa_9280,

Have you tried uploading a new NuGet package and tried downloading it? I would just like to rule out the directory and file renaming. I'm running the core version locally and I'm not currently able to recreate the authentication issues in my tests.

Thanks,
Rich

Hi @viceice,

Nothing is sticking out to me that there is an issue. Your hardware looks fine (without knowing everything else running on the server/kube pods).

It looks like it is hanging when trying to load the current database schema version. The code for both mono and .net core does not differ for this component. Is there anything that is different from your progetmono and progetcore start scripts in kubernetes? I would put some enphasis around the networking piece in kubernetes.

Thanks,
Rich

Hi @barnaby-williams_8489,

This is just a manual copy of the files.

Thanks,
Rich

Hi @nuno-guerreiro-rosa_9280,

If you upload a new package, can you download it then? That would be the best way to verify the casing change did not affect the authentication.

Also, what user directory are you using? Are you using the built-in user directory, Active Directory, or LDAP Legacy?

Thanks,
Rich

Hi @jim-pg_1173,

I was able to identify the issue. I created a ticket to track the fix, PG-1831, this will be released in the next version of ProGet. ProGet 5.3.13 will be released this Friday, Oct 9th, 2020. I will reply back if anything changes.

Thanks,
Rich

Hi @jim-pg_1173,

Thanks for posting this here. The GitHub ticket is very helpful for this. Let me do some investigating and I'll get back to you about this.

Thanks,
Rich

Hi @nuno-guerreiro-rosa_9280,

I tested the scenario where I setup anonymous to view only and a user to download only and it successfully authenticated and downloaded the package for me. Would you be able to share the custom tasks you are using for the anonymous user and the user that has download only?

Here is what I setup:

View Only

Download Only

If you give the user View & Download rights, does it work?

Thanks,
Rich

Hi @viceice,

There shouldn't be any issue with your SQL Server version, but I will do some testing on that version to see if I can recreate the issue. SQL Server 2014 is technically deprecated by Microsoft, but we are not using any functionality that wouldn't work with it. I'll let you know if I find anything on that front.

As for the 100% CPU usage, I'm going to reach out to my colleague internally to see if there are any extra debug settings that can be enabled, but I do not think there is. Do you have the docker host throttling what hardware can be used with that container? If so, what are the restrictions for it? Also, are you able to share what hardware specs are for your Docker host?

Thanks,
Rich

Hi @viceice,

I'm having trouble recreating this issue. Could you try using the IP address as the SQL Server data source instead of db02? There isn't any difference in the startup between the dotnet core version and the mono (outside of the image base that is). If you let it run, do you get any timeout or cannot find server error?

Thanks,
Rich

Hi @viceice,

Can you tell me how many feeds you have and what types those feeds are? Also, does your ProGet database user have db_owner on the ProGet database or just the ProGetUser_Role?

Thaks,
Rich