You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.
I ran start.sh in Cygwin and it succeeded, but I saw the following output:
./start.sh: line 30: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe: command not found
As you can see, this occurred at start.sh#L30, which is where the script is executing VBoxManage so that it can set the VM_EXISTS_CODE variable. As a result of the command failing, the variable was set to 1. Should the command have succeeded, the variable would still have been set to 1, because I did not have any Docker VMs at that time. This is why everything still went smoothly despite the error.
The VBoxManage.exe file does exist at that location, but Cygwin doesn't seem to support executing files using their Windows-format path.
Something like this to could be used to convert the path for Cygwin:
if [ "$(uname -o)"=="Cygwin" ];then
VBOXMANAGE="$(cygpath -u "$VBOXMANAGE")"fi
The text was updated successfully, but these errors were encountered:
Thanks for this. 'docker run hello-world' worked after above fix.
Running 'docker run -it ubuntu bash' however failed and gave me a "cannot enable tty mode on non tty input. try prepending command with mintpy" error.
Might be related to: moby/moby#12469
I then ran the start.sh in a normal Windows cmd.exe (cmd has access to cygwin commands since i added c:/cygwin/bin to my PATH hence why i can run a .sh shell script in there).
Now I can run all the docker runs in their intro tutorial so far.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I ran
start.sh
in Cygwin and it succeeded, but I saw the following output:As you can see, this occurred at start.sh#L30, which is where the script is executing VBoxManage so that it can set the
VM_EXISTS_CODE
variable. As a result of the command failing, the variable was set to1
. Should the command have succeeded, the variable would still have been set to1
, because I did not have any Docker VMs at that time. This is why everything still went smoothly despite the error.The
VBoxManage.exe
file does exist at that location, but Cygwin doesn't seem to support executing files using their Windows-format path.Something like this to could be used to convert the path for Cygwin:
The text was updated successfully, but these errors were encountered: