-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
The system cannot open the device or file specified 'NuGet-Migrations' #91987
Comments
Update: when I run the container as root, the problem disappears. But even so, that error is misleading. |
Tagging subscribers to this area: @mangod9 Issue DetailsDescriptionIn a CI build, in the official sdk docker image, I run
Reproduction Stepsinside the sdk container:
Expected behaviorNo error Actual behaviorError Regression?uknown Known Workaroundsnone Configurationmcr.microsoft.com/dotnet/sdk:7.0.400-bookworm-slim-amd64 Other informationMight be related to NuGet/Home#12159 and #80619, but those have been locked. If I remove that offending line, I can build the docker image. If I then run that image and do something as simple as
|
cc @kouvel |
This could be similar to #80619. If the container get set up as root or some other user and then a different user uses the container, a workaround may be to delete the
There is an issue for that, which would hopefully be addressed soon: #89090 |
Thanks. I'll try the new version when it's released to see if it fixes this. Is it one of those fixes that's released every month or so? |
Yes, the change should be in the next version that is released, 6.0.23 and 7.0.12. |
@kouvel this might not be a System.Threading specific issue. I'm also seeing this failure in 7.0 CI runs for JIT HardwareIntrinsics in WASM like this one (completely unrelated):
Output (Expand):
|
My understanding was that some of these tests in WASM have a build portion that runs as part of the test run. The exception is being thrown under |
Here's another one from today, found in 6.0:
|
That unfortunate. It seems the release/6.0 branch is currently using the latest runtime that would have the fix. The fix may not fix things if the permissions issue is retained, such as if this ran on a VM where an unfixed runtime was used, and would be unlikely if a container is being used (unless the permissions issue occurred during container setup). PR #92603 added some additional diagnostics info, if this happens in .NET 9 CIs hopefully we'll get more info about what's happening. |
@kouvel One more hit in 6.0, now in the branding PR for 6.0.26:
|
Continues affecting 6.0. Example: #99787
|
@carlossanlop I'm facing the same issue with 8.0.2 do you know any workaround for this? thanks! |
We're seeing
with 8.0.101 on our CI (linux, ubuntu 22.04, GitHub actions). Is there any progress on this issue? |
Description
In a CI build, in the official sdk docker image, I run
dotnet nuget locals all --clear
, and get this:Reproduction Steps
inside the sdk container:
Expected behavior
No error
Actual behavior
Error
Regression?
uknown
Known Workarounds
none
Configuration
mcr.microsoft.com/dotnet/sdk:7.0.400-bookworm-slim-amd64
Other information
Might be related to NuGet/Home#12159 and #80619, but those have been locked.
If I remove that offending line, I can build the docker image. If I then run that image and do something as simple as
dotnet nuget
it will give the same error as above.Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=426482
Error message validated:
The system cannot open the device or file specified. : 'NuGet-Migrations'
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 10/4/2023 1:44:58 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: