-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Long Execution Time for dotnet restore in OpenShift Build Pipeline #13327
Comments
Since it also seems to be slow for |
@jeffkl I try to ping the nuget.org during the |
After investigating, this issue isn't relevant to the Nuget. The cause of workload on OpenShift during dotnet restore. We can close this one. |
@linhvuquach Thanks for providing an update. I'm glad to hear that you were able to identify the root cause. Closing ticket. |
Impact
It's more difficult to complete my work
Describe the bug
During our build pipeline execution on OpenShift, we've encountered a significant delay specifically with the dotnet restore command in the Dockerfile. This delay is causing notable slowdowns in our overall build process.
My Dockerfile
My nugget.config
Version
I'm using openshift version 4.
Current Result
Repro Steps
I can build a simple Dockerfile .NET API application. Then you can set up a simple trigger CI to Openshift to build the pipeline.
At the step build the pipeline you will face this issue (dotnet restore).
Expected Behavior
The Openshift pipeline can build successfully the Dotnet Docker image.
Screenshots
No response
Additional Context and logs
Additional Information
ENV DOTNET_NUGET_SIGNATURE_VERIFICATION=false
in Dockerfile. But it didn't resolve yet.npm install
step. I think the same concept with thedotnet restore
command.aspnet:8.0
toaspnet:7.0
. It still didn't successAny insights or guidance will be expected. Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered: