Unable to restore packages on Ubuntu 18.04 (3.0 preview7)
See original GitHub issueHello,
I’m trying to get the latest 3.0 preview7 working on my Ubuntu 18.04 remote server using the latest tar.gz from core-sdk for Linux x64. The dotnet command is working but if I try to install new templates eg. for blazor, the restore process fires up but then -> nothing. The process stays in my process list:
After running the command, that’s all that happens:
I also tried dotnet restore
with a newly created AspNetCoreApp project but the result is the same.
Any ideas? Do I miss something here? Thanks in advance!
Steps to reproduce
- Download latest preview7 tar.gz from core-sdk for Linux x64
- unpack with
tar zxvf dotnet-sdk-latest-linux-x64.tar.gz -C ./dotnet3
(create destination folder befor extracting) - setup environment variables
export DOTNET_ROOT=$HOME/dotnet3
&export PATH=$PATH:$HOME/dotnet3
, I’m using zsh so they goes into my .zshrc (or .zprofile) - reopen shell
- run
dotnet new -i "Microsoft.AspNetCore.Blazor.Templates::3.0.0-preview7.*"
- restore process hangs with no output or any message
Also with preview6 bits as root or user, does not make any difference. It works on Windows 10 and WSL (Ubuntu 18.04) perfectly!
Expected behavior
The command should restore necessary files from Nuget and install new templates so they can be used with dotnet new
Actual behavior
Restore process hangs with no output or any message.
Environment data
dotnet --info
output:
.NET Core SDK (reflecting any global.json):
Version: 3.0.100-preview7-012398
Commit: 028dd7635a
Runtime Environment:
OS Name: ubuntu
OS Version: 18.04
OS Platform: Linux
RID: ubuntu.18.04-x64
Base Path: /home/---/dotnet3/sdk/3.0.100-preview7-012398/
Host (useful for support):
Version: 3.0.0-preview7-27813-06
Commit: 5cfc2cab25
.NET Core SDKs installed:
3.0.100-preview7-012398 [/home/---/dotnet3/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.0.0-preview7.19311.5 [/home/---/dotnet3/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.0.0-preview7-27813-06 [/home/---/dotnet3/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
Issue Analytics
- State:
- Created 4 years ago
- Comments:17 (9 by maintainers)
Top GitHub Comments
Our Build issues were resolved by setting
MSBUILDDISABLENODEREUSE=1
in this PR.The effect of
-m:1
seemed to allow the MSBuild execution to continue, but then the next MSBuild without-m:1
would hang. I did not use this in my PR.@rainersigwald suggested I run this to provide diagnostics to MSBuild team:
MSBUILDDEBUGCOMM=1
MSBUILDDEBUGPATH=/path/to/some/directory
I ran this directly on the Linux machine, and it still hanged on the same MSBuild invocation.
It repeats a couple dozen times:
Failed to connect to pipe MSBuild57710. The operation has timed out.
It appears to stop writing to the file, as hours later, the log had still not been modified. linuxOutput.txtThanks for the suggestion, and I’ve referenced an issue to revert this fix once this Issue is closed.
FYI I have this issue if I’m running WSL2 and connected to VPN on my host. It’s the same issue as VS Code being unable to update. Just drop your VPN connection and magic happens.