On WSL Ubuntu 18.04 dotnet tool install -g Cake.Tool and Octopus.DotNet.Cli fails
See original GitHub issueThe combination of WSL and Ubuntu 18.04 seems to cause issues with .NET global tools.
Steps to reproduce
dotnet tool install -g Cake.Tool
dotnet tool install -g Octopus.DotNet.Cli
Expected behavior
+ You can invoke the tool using the following command: dotnet-cake
+ Tool 'cake.tool' (version '0.30.0') was successfully installed.
+ You can invoke the tool using the following command: dotnet-octo
+ Tool 'octopus.dotnet.cli' (version '4.41.0') was successfully installed.
Actual behavior
- The settings file in the tool's NuGet package is invalid: Settings file 'DotnetToolSettings.xml' was not found in the package.
- Tool 'cake.tool' failed to install. Please contact the tool author for assistance.
- The settings file in the tool's NuGet package is invalid: Settings file 'DotnetToolSettings.xml' was not found in the package.
- Tool 'octopus.dotnet.cli' failed to install. Please contact the tool author for assistance.
Environment data
dotnet --info
output:
.NET Core SDK (reflecting any global.json):
Version: 2.1.401
Commit: 91b1c13032
Runtime Environment:
OS Name: ubuntu
OS Version: 18.04
OS Platform: Linux
RID: ubuntu.18.04-x64
Base Path: /usr/share/dotnet/sdk/2.1.401/
Host (useful for support):
Version: 2.1.3
Commit: 124038c13e
.NET Core SDKs installed:
2.1.401 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.3 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.3 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.3 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
I’ve successfully installed Cake.Tool
and Octopus.DotNet.Cli
using 2.1.401 on
- Docker
- microsoft/dotnet:2.1-sdk
- ubuntu:18.04
- ubuntu:16.04
- fedora:28
- centos:centos7
- WSL
- Ubuntu 16.04
- openSuse Leap 42
- Debian 9
- Windows
- Mac
So doesn’t seem package related but rather a specific environment issue.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:8 (4 by maintainers)
Top Results From Across the Web
On WSL Ubuntu 18.04 dotnet tool install -g Cake. ...
On WSL Ubuntu 18.04 dotnet tool install -g Cake.Tool and Octopus.DotNet.Cli fails #9731 · + You can invoke the tool using the following...
Read more >Octo fails to install when using the .Net Core CLI - Integration
I am attempting to install Octo on to my machine using the .Net Core CLI. ... Tool 'octopus.dotnet.cli' failed to install.
Read more >Troubleshoot .NET tool usage issues
NET tool, which can be a global tool or a local tool. This article describes the common root causes and some possible solutions....
Read more >Unable to run octo cli - Integration
I'm installing it with dotnet tool install --global Octopus.DotNet.Cli --version 9.0.0. When I run dotnet octo I get
Read more >dotnet-ef does not exist - Windows 10 WSL (Ubuntu)
Finally I found the solution! I've tried to export the PATH variable export PATH="$PATH:$HOME/.dotnet/tools" as @kapsiR mentioned.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing in favor of issue https://github.com/dotnet/cli/issues/10101
We are seeing a very similar issue here: https://github.com/NuKeeperDotNet/NuKeeper/issues/433
Install on Ubuntu 18.04 fails, This is for both Ubuntu hosted on WSL or on a cloud VM. Error is:
The error is not correct, that file exists. This might be a capitalisation issue - the tool name is “NuKeeper”. Or it might be due to package signing failing.
We are considering changing the tool name caps to “nukeeper” is it is confirmed that this is necessary for Linux support. But we can’t tell the cause since the error message is false. The docs on NETCore global tools don’t say anything about naming requirements for use in Linux. Are there any, particularly with regard to capitalisation?