That didn't work, but for a different reason: $ vagrant up failed generating SSL CA artifacts
The system call didn't create directory "ssl": dmahar@PC09 ~/vagrant/coreos/coreos-kubernetes/single-node $ ls -la total 44 drwxr-xr-x+ 1 dmahar Utilisa. du domaine 0 Aug 29 16:42 . drwxr-xr-x+ 1 dmahar Utilisa. du domaine 0 Aug 29 16:29 .. -rw-r--r-- 1 dmahar Utilisa. du domaine 14 Aug 29 16:29 .gitignore drwxr-xr-x+ 1 dmahar Utilisa. du domaine 0 Aug 29 16:42 .vagrant -rwxr-xr-x 1 dmahar Utilisa. du domaine 318 Aug 29 16:29 conformance-test.sh -rw-r--r-- 1 dmahar Utilisa. du domaine 437 Aug 29 16:29 kubeconfig -rw-r--r-- 1 dmahar Utilisa. du domaine 297 Aug 29 16:29 README.md -rw-r--r-- 1 dmahar Utilisa. du domaine 27395 Aug 29 16:29 user-data -rw-r--r-- 1 dmahar Utilisa. du domaine 2346 Aug 29 16:42 Vagrantfile I'll tweak it to try to get it to work. Derek On Monday, 29 August 2016 16:33:46 UTC-4, Alban Crequy wrote: > > On Mon, Aug 29, 2016 at 4:22 PM, Derek Mahar <derek...@gmail.com > <javascript:>> wrote: > > How might I fix the error that I encounter when, in a Cygwin bash shell, > I > > run "vagrant up" in single-node or multi-node of > > https://github.com/coreos/coreos-kubernetes? > > > > dmahar@PC09 ~/vagrant/coreos/coreos-kubernetes/single-node > > $ vagrant up > > '.' is not recognized as an internal or external command, > > operable program or batch file. > > failed generating SSL CA artifacts > > It seems to come from this line in the Vagrantfile: > > system("mkdir -p ssl && ./../lib/init-ssl-ca ssl") or abort ("failed > generating SSL CA artifacts") > > It could be Windows requesting the path separator "\" instead of "/". > I am not sure whether "system" is executing a cygwin shell or a > Windows command. > > Does it work with the following? > > system("C:\cygwin\bin\run.exe /bin/sh -c 'mkdir -p ssl && > ./../lib/init-ssl-ca ssl'") or abort ("failed generating SSL CA > artifacts") >