Octo fails to install when using the .Net Core CLI

reliability
(David Gard) #1

I am attempting to install Octo on to my machine using the .Net Core CLI.

I’ve found two sets of instructions for this -

Although the first references a specific version, they both say to use dotnet tool install Octopus.DotNet.Cli --global.

However, when I try to install Octo this way I am met with an error -

The tool package could not be restored.
Tool ‘octopus.dotnet.cli’ failed to install.

I suspect that I may need to use the --add-source parameter so that Octo is found, but I cannot see anywhere in the documentation what that source should be?

Note: My .NET Core version is 2.2.105.

Thanks,
David

(David Gard) #2

I have now been able to fix this issue.

The installation failed because I have a private NuGet repo as a source, but connection to it failed, so NuGet threw an error. Since the .Net Core CLI uses NuGet to install packages, it in turn failed.

I was able to work around the problem by using the --ignore-failed-sources parameter, which is undocumented at the time of writing.

Thanks,
David

(Dalmiro Grañas) #6

Hi David,

Thanks for reaching out!

Yep that bug seems to be the root cause of that issue. Thanks for taking to time to share your findings here :slight_smile:

Best regards,
Dalmiro