Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Workload install copying across mounts error

See original GitHub issue

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 a Invalid cross-device link. error (

Repro: Workload install using WSL

Error output:

/mnt/c/code/tmp2$ ./dotnet workload install microsoft-net-sdk-blazorwebassembly-aot Skip NuGet package signing validation. NuGet signing validation is not available on Linux or macOS . Updated advertising manifest Updated advertising manifest Updated advertising manifest Updated advertising manifest Failed to update the advertising manifest is not found in NuGet feeds"… Updated advertising manifest Updated advertising manifest Installing workload manifest version 30.0.100-preview.5.28. Workload installation failed, rolling back installed packs… Installing workload manifest version 11.0.200-ci.main.256. Installation roll back failed: Failed to install manifest version 11.0.200-ci.main.256: The transaction has aborted… Workload installation failed: Failed to install manifest version 30.0.100-preview.5.28: Invalid cross-device link.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

jonathanpepperscommented, Jun 24, 2021

Saw this on Windows, might be related:

sfoslundcommented, Jun 23, 2021

Yes, I think this was all a result of, 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 --temp-dir option and specifying a temp location within the same mount as the dotnet installation.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Failed to pair to Mac with error "Could not install workload ...
I used WinSCP to connect to my Mac from Windows and copied the folder C:\Program Files\dotnet\sdk-manifests\6.0.300\
Read more >
Problem installing Android workload for MAUI Visual ...
I started a new CometApp project and I get the following error: NU1012 Platform version is not present for one or more target...
Read more >
Mount a virtual file system on a Batch pool - Azure
Connect to the node over RDP. Run the command you copied to mount the file share. Note any error messages in the output....
Read more >
RHEL mount hangs: nfs: server [...] not responding, still trying
Problem between the NFS Client and NFS Server. For example, overloaded, mis-configured, or malfunctioning switches, firewalls, or networks may ...
Read more >
Troubleshoot .NET tool usage issues
Discover the common issues when running .NET tools and possible solutions.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found