No symlinked folder, errors upon vagrant reload

I ran vagrant reload as suggested in another question thread from a user who also has no symlinked folder. The reload gave me errors. [default] Configuring and enabling network interfaces... /Applications/Vagrant/embedded/gems/gems/net-ssh-2.6.6/lib/net/ssh/transport/packet_stream.rb:87:in `next_packet': connection closed by remote host (Net::SSH::Disconnect)

This is after having destroyed the VM and rebuilt it from scratch. Any ideas?

Sorry You must be a logged in, registered user to answer a question.

Answers

You shouldn't have to do vagrant reload whenever you come back to work on the lessons. You should only have to vagrant up and then vagrant ssh to get in and start the development server.

The /vagrant directory only exists on the VM. On your local system, it's whatever directory you did vagrant up in.

kennethlove (Staff) on
Your tutorials are fantastic, by the way. Thank you for doing this.
Devon Campbell on
You're right. This was a misunderstanding on my part. Thank you for your help!
Devon Campbell on

When you run vagrant up, you get this error? Or after a successful vagrant up/vagrant halt cycle?

kennethlove (Staff) on
I only get that when I run `vagrant reload` as suggested in the other thread. `vagrant up` seems to work although I get `dpkg-preconfigure: unable to re-open stdin: No such file or directory` and a couple `stdin: is not a tty` errors. `vagrant halt` seems to work without issue. I have no folder on my local file system, though, or else I'm misunderstanding where it should be. It's not in the folder I created for the project, the .vagrant folder inside that, or the .vagrat.d folder inside my user directory.
Devon Campbell on