Vagrant on Windows - any way to stop provisioning with Ctrl-C?

Very often, when I start the boot book on a Vagrant VM from Windows, I need to stop in the middle of something by pressing Ctrl + C. This happens if ansible becomes irrelevant or there is some error that we need to fix as soon as possible, so there is no need to wait for completion creation.

The bottom line is that Ctrl + C does not work, some ruby.exe processes get stuck in the process tree. Any subsequent roaming teams fail until you manually chop these ruby โ€‹โ€‹processes.

I also use to kill all stuck processes in Python in a virtual machine before launching new software.

How can I process it in more detail?

+5
source share
1 answer

I found this problem also on Windows and using Puppet Apply. The only way I can happily kill him is by opening another terminal / cmd and then vagrant ssh -- sudo pkill puppet . This gracefully completes the process and allows me to regain control of my first terminal again.

0
source

All Articles