-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 #28612
Comments
I had a same issue and my workaround is like that : ENV DOTNET_USE_POLLING_FILE_WATCHER=false
ENV NUGET_XMLDOC_MODE=skip
ENV NUGET_CERT_REVOCATION_MODE=offline use Dockerfile for single service:
|
This issue may occur when the build pod reaches its limit. Please try adding more resources to the Tekton builder pod, as shown below:
Read more at: https://github.com/tektoncd/pipeline/blob/main/docs/pipelineruns.md#specifying-taskrunspecs |
It works for me if I add |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
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
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: