-
Notifications
You must be signed in to change notification settings - Fork 1.1k
dotnet workload install wasm-tools does not install on Linux #31685
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
Comments
Aha, found a resolution: I decided to ditch the SDK bundled with Ubuntu, and installed it through the MS package feed. And now it correctly installs. I would suggest documenting this somewhere perhaps? I think the issue can be closed though. For anyone wanting to switch to Microsoft feed as well:
|
Installing a workload with the a bundled SDK should work by leaving out
MS builds require |
I tried it without |
This is what I get when using the distro packages on Fedora:
Can you share the output of:
This should find a file at |
Hi, as I've already switched to the MS package feed I can't test this, but perhaps I can try this on another device |
cc @mirespace |
Taking a look... thanks @tmds! |
Hi, I could reproduce the issue (same results using
The command for checking the userlocal file fails if I don't use the -f to follow symlinks:
In a VM (using Multipass), I couldn't execute the workload command without
but the same result is obtained:
|
Good. This makes install work without
I imagine this happens because you ran the command with Try this:
|
Thanks, it worked! And now it lists the installed workloads:
|
Great! For some extra context: when the installable workload feature got added to the sdk, we wanted to avoid the A source-build sdk includes a |
Hi @tmds, I was checking different installations to see if this is something we must consider from the debian packaging/installation point of view, and I reproduced the issue in a LXC container (Ubuntu Jammy) with our lastest ubuntu debs from ubuntu.archive : installed successfully, but the listing doesn't.
So I check for the .dotnet folder under the user home folder, and it is not there: it is under /tmp (is this OK?):
and a file for wasm-tools as a installed workload can be found at:
I'd appreciate any thoughts/suggestions on this... thank you in advance. |
This is unexpected. The SDK should anyhow create a |
Not to interrupt your conversation, but should I reopen this issue, since it's confirmed? Or is this the wrong place since it seems Ubuntu-specific? |
There's some other issue going on as it seems the .NET SDK in @mirespace's LCX container environment has trouble finding the HOME directory. |
Yes, it is:
|
@mirespace how do I reproduce your environment? |
@tmds, the following are the steps to install LXD and creating the Jammy VM/Container (and reproduce the initial issue here). I use Ubuntu also like host, but you can do it on Fedora or Windows among others as well :
If you have any problems, please let me Know |
@mirespace this is messing up sdk/src/Cli/dotnet/SudoEnvironmentDirectoryOverride.cs Lines 23 to 43 in 4e8e433
If you |
Thanks @tmds! |
I run
sudo dotnet workload install wasm-tools
, it says that installation was successful.When I then run
dotnet workload list
it shows no workloads.Output of installation:
Output of
workload list
:Further technical details
dotnet info:
Note: The OS
tuxedo
is basically Ubuntu.The text was updated successfully, but these errors were encountered: