Virtualization

After the earlier Vagrant does not respond , it would be a problem if the vagrant ssh command became unusable, so — belatedly — I set up connecting over plain SSH. Connecting with plain ssh rather than using vagrant ssh seems to be faster and more responsive In my own Vagranfile the connection is already bridged, and the default port is 2222 Copy config.vm.network "public_network", ip: "192.168.1.10", bridge: "en0: Ethernet" If you have not configured the network part, write it as follows [Read More]

I run vagrant on a Mac (Mojave), but recently I hit a situation where vagrant would not respond at all Copy $ vagrant ssh $ vagrant status $ vagrant info $ No matter which command I type, there is no reaction whatsoever!? Thinking that vagrant might be broken, I ran brew reinstall vagrant After that the vagrant command came back, but this time I got the error below Copy $ vagrant status Traceback (most recent call last): 2: from /opt/vagrant/embedded/gems/2.3.4/gems/vagrant-2.3.4/bin/vagrant:111:in `<main>' 1: from /opt/vagrant/embedded/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require' /opt/vagrant/embedded/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require': cannot load such file -- vagrant (LoadError) 12: from /opt/vagrant/embedded/gems/2.3.4/gems/vagrant-2.3.4/bin/vagrant:111:in `<main>' 11: from /opt/vagrant/embedded/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:147:in `require' 10: from /opt/vagrant/embedded/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:158:in `rescue in require' 9: from /opt/vagrant/embedded/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:158:in `require' … /opt/vagrant/embedded/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require': cannot load such file -- google/protobuf_c (LoadError) ~/vagrant ❯ w google/protobuf_c? Is this a ruby related error?? [Read More]

Symptoms I run several servers in Docker containers with Vagrant on my Mac, but the guest OS I had started with Vagrant stopped coming up, and neither vagrant ssh nor vagrant halt worked any more. Copy $ vagrant halt The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below: Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed. Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires this to be available on the PATH. If VirtualBox is installed, please find the `VBoxManage` binary and add it to the PATH environmental variable. VirtualBox cannot be found? Did it disappear? [Read More]