I have a fresh Windows 10 64-bit install, which I'm attempting to set up for development.
I have
- downloaded and installed cmder, then rebooted
- downloaded and installed Vagrant, then rebooted
- downloaded and installed VirtualBox, then rebooted
- set
VAGRANT_HOME=c:\vagrant
- used
VBoxManage setproperty machinefolder c:\virtualbox-machines
- acquired my department's VagrantFile, and modified it to suit my filesystem.
In cmder, if I now run
vagrant box add http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_centos-7.0_chef-provisionerless.box --name chef/centos-7.0
I get no output. No failure codes, no windows errors, no logs from vagrant. The same is true of all vagrant commands, up to and including vagrant --version
and vagrant --help
. Other commands work fine in cmder.
However, if I run a basic command line, cmd.exe
, then the vagrant box add
command completes correctly. An, as far as I know, identical setup worked under Windows 7 32-bit.
Can anyone suggest what might be going wrong?
ConEmu 161022 [32]
(which is a little odd, because it's a Windows 10 64-bit install - but that's what came with cmder). There's no point getting screenshots - there is literally nothing after running a vagrant command. Just one blank line, then the next prompt.vagrant --version
.stable
andlatest
version ofcmder
both facing this issue. I asked him to useconemu
directly instead, he installedconemu
usingchocolatey
and now hisvagrant
command works.