-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Workload install copying across mounts error #18450
Comments
I ran into this too on dotnet/runtime#54451 . And switched to using copying individual files with |
Workloads on linux appear to be very broken due to this with a very recent SDK I get
|
Yes, I think this was all a result of #17860, where we changed to using the machine's default temp location, which on linux is often on a different mount from the dotnet install location. I'll get a PR out to fix this today but in the meantime it can be worked around by using the |
Saw this on Windows, might be related: #18516 |
The files on disk workload install needs to copy files into both the user's home (advertising manifests) and the dotnet directory (packs, installed manifests). This can cause problems with those are under different mounts, for example, the default user home on linux is
/home/...
and you could potentially install dotnet to/mnt/...
. This is problematic because install uses one temp directory and has to be able to copy from that temp directory into both the home and dotnet directories. When the mounts for these locations conflict we run into aInvalid cross-device link.
error (dotnet/runtime#31149).Repro: Workload install using WSL
Error output:
The text was updated successfully, but these errors were encountered: