Open dcode opened 5 years ago
I have exactly the same problem. Ignition plugin says it only works for virtualbox so I guess it fails the ssh key
Hello, I have a similar issue. My vagrant version is 2.2.3 I modified https://github.com/coreos/coreos-vagrant/blob/master/Vagrantfile and the machine was able to start. Basically I had to add vmware_desktop to the providers eg: ["vmware_fusion", "vmware_workstation"] -> ["vmware_fusion", "vmware_workstation", "vmware_desktop"]. However, it takes around 30 minutes for the CoreOS kernel to boot.
Issue Report
Bug
Container Linux Version
Never got this far
Environment
VMware Fusion 11 (also tried with 10) MacOS 10.13.6 Vagrant 2.2.0 (also tested with 2.1.4)
Expected Behavior
VM would boot and provision the same as the Virtualbox box.
Actual Behavior
Vagrant is unable to reach the VM via SSH to start the provisioning.
Reproduction Steps
I manually installed
vagrant-ignition
in another directory to get out of the loop. Then I noticed it still wasn't quite working due to changes in vagrant to a unified desktop provider. I then added "vmware_desktop" to each of the vmware blocks. After that, running again produces the following:Other Information
I ended up installing Virtualbox to test and that worked as expected.