![]() Unfortunately, this is a clash with GOW - uninstall GOW.ĭo this and Kitematic uses an internal SSH bin and this error is not seen.Hmmm. It actually fails at the SSH call (using GoW), actually callingĬ:\Program Files (x86)\Gow\bin\ssh.bat that calls plink…Ĭ:\Program Files (x86)\Gow\bin\ssh.bat},(default) DBG | About to run SSH command:,(default) DBG | exit 0,(default) DBG | SSH cmd err, output: exit status 1: 'C:\Program' is not recognized as an internal or external command, So I assume it is a Docker Toolbox config issue as it is not using the SSH binary set in the PATH variable… > docker-machine ip my-machine Error getting IP address: Something went wrong running an SSH command! command : ip addr show dev eth1 err : exit status 1 output : 'C:\Program' is not recognized as an internal or external command, operable program or batch file. Kitematic hangs for an age at 100% then dumps out the log with the error in OP.īut, it’s not a Kitematic error: I can reproduce using Docker CLI (docker-machine) also: The latest Windows updates have been applied. Processor Intel® Core™ i7-4710HQ CPU 2.50GHz, 2501 Mhz, 4 Core(s), 8 Logical Processor(s) ![]() System SKU LENOVO_MT_80DU_BU_idea_FM_Lenovo Y70-70 Touch Maybe this explains why I can launch Kitematic from the terminal since I escape the spaces in the directories? In any event, I hope this bug is fixed in a future Docker Toolbox release. $ /c/Program\ Files/Docker\ Toolbox/kitematic/Kitematic.exeįrom the error message in Scenario 1, it appears the space in the directory name is preventing the app from executing correctly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |