search

stackfoundation / issues

Public issue tracker for stack.foundation
0 stars 0 forks source link

"Path could not be found" when starting in Windows #4

Open christian-laakmann opened 6 years ago

christian-laakmann commented 6 years ago

Hi,

I have an issue when trying to run a workflow on Windows:

> sbox run <workflow>
Setting up and starting a local Kubernetes v1.7.2+$Format:%h$ cluster...
Starting Sandbox VM...
Creating new host
Downloading C:\Users\<user>\.sbox\cache\boot2docker.iso from file://C:/Users/<user>/.sbox/cache/iso/minikube-v0.23.1.iso...
Error starting host: Error creating host: Error executing step: Creating VM.
: open /Users/<user>/.sbox/cache/iso/minikube-v0.23.1.iso: Das System kann den angegebenen Pfad nicht finden..

 Retrying.

Error starting host: Error creating host: Error executing step: Creating VM.
: open /Users/<user>/.sbox/cache/iso/minikube-v0.23.1.iso: Das System kann den angegebenen Pfad nicht finden.

"Das System kann den angegebenen Pfad nicht finden." translates to "System could not find the required path"

The issue seems to be that my project files are not located on the windows root hard disk. I'm running from D:\path\to\my\project instead of C:...

When I moved sbox to C:... the error disappeared.

rchodava commented 6 years ago

Thanks for reporting this. This is indeed an issue - the file URL that is constructed shouldn't have the drive letter with a colon - it should be file://c/Users... When that URL is used later, only the portion after the drive letter, i.e., /Users/... will get used if there is a colon int he URL. We'll take a look at fixing this, thanks!