-
Notifications
You must be signed in to change notification settings - Fork 82
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
Building solution with --runtime fails with error LIB003 #489
Comments
Same issue on v2.1.76. Is there any workaround? |
I am having a similar issue; I dont have the runtime options, but the project does have them in the proj like this ;
I get this error; pretty consistently
on version 2.1.161, but had it on earlier versions too. |
We are experiencing this sporadically as well. Is there any update? |
I would also like to tack onto this issue. I am seeing it while restoring a net6.0 asp.net web app in a docker container. It's important to note that while the web app doesn't have multiple runtimes, and I wasn't using the CLI options to specify one, the app did use some legacy packages in .Net Framework. I had been using the dotnet core docker image as my build, so I tried using a framework image instead to see if that helped - and it did! So for anyone stuck on this, I might recommend trying a Framework container and see if it helps, especially if you have legacy/old Nuget packages that run in Framework (even if your web app is dotnet core) |
@Hoai-Phong can you share the libman.json snippet for that library so I can try to reproduce the issue? |
@jimmylewis
, |
Functional impact
Build fails in CI server
Minimal repro steps
I have a build pipeline that runs each step in the nano sdk container on Windows 2019 (microsoft/dotnet:2.2.103-sdk-nanoserver-1809). The source code folder is mapped into the container as a volume.
My solution contains a web project, a couple of support projects and a couple of test projects that depend on the web project
Step 2 fails with multiple instances of error LIB003, each for a different file. The files in question are present
Expected result
The build would work
Further technical details
--runtime win-x64
option works.My guess is that there's a race condition between concurrent downloads of the packages caused by builds of the test projects. When
--runtime
is specified the output shows 2 instances ofwhereas without it only 1 restore is done.
The text was updated successfully, but these errors were encountered: