[Nuget] update package-lock.json fail when package is in private repository #34487
Replies: 3 comments 5 replies
-
I forgot to add I'm using image with tag 39.179-full. I also tried to add private repository to default Nuget.config file but it did not help. It looks like that renovate create its own config file and use it. |
Beta Was this translation helpful? Give feedback.
-
Does Renovate itself look up dependencies from the right registries, including private? If so, how do you know? |
Beta Was this translation helpful? Give feedback.
-
Hi there, The logs you provided are insufficient to help you. Please provide more logs, or more detailed logs, so we can help you. Be sure to include DEBUG logs, and don't excessively redact or truncate them. If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here. Read the Renovate docs, Troubleshooting to learn more about getting the correct logs. Thanks, the Renovate team |
Beta Was this translation helpful? Give feedback.
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
On-prem K8s
Please tell us more about your question or problem
Hello,
I'm using on-prem renovate in private K8s. When I try to update dependencies in .NET project where is turned on to create package-lock.json, update itself works but update of lock files failed because in my project is reference to packages which are in private Nuget repository. This repository is properly configured and renovate are able to find new versions of packages in it but it looks like that it is not used during dotnet restore command run.
When I tried to attach to container and list configured NuGet repositories I saw only standard nuget.org repo. Also in log I see that restore tries to find package in nuget.org only.
What I'm doing wrong?
Thank you
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions