Hey there, Are you asking how to get back into the virtual machine after exiting? You should be able to do so by typing
vagrant ssh That will put you back into the machine you brought up and provisioned with Vagrant. On Fri, Feb 22, 2019 at 6:20 AM 'Karen Goh' via Vagrant < [email protected]> wrote: > I was playing with several command line and then I wanted to continue but > just don't know how to vagrant up again after I typed exit > > vagrant@vagrant-ubuntu-trusty-64:~$ do-release-upgrade > Checking for a new Ubuntu release > Get:1 Upgrade tool signature [819 B] > Get:2 Upgrade tool [1,260 kB] > Fetched 1,261 kB in 0s (0 B/s) > authenticate 'xenial.tar.gz' against 'xenial.tar.gz.gpg' > extracting 'xenial.tar.gz' > [screen is terminating] > vagrant@vagrant-ubuntu-trusty-64:~$ vagrant status > The program 'vagrant' is currently not installed. To run 'vagrant' please > ask your administrator to install the package 'vagrant' > vagrant@vagrant-ubuntu-trusty-64:~$ x > x: command not found > vagrant@vagrant-ubuntu-trusty-64:~$ > vagrant@vagrant-ubuntu-trusty-64:~$ exit > logout > Connection to 127.0.0.1 closed. > > C:\Users\Karen.Goh\VMLinux>vagrant up > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Checking if box 'ubuntu/trusty64' version '20190206.0.0' is > up to date... > ==> default: Machine already provisioned. Run `vagrant provision` or use > the `--provision` > ==> default: flag to force provisioning. Provisioners marked to run always > will still run. > > C:\Users\Karen.Goh\VMLinux>vagrant provision > ==> default: Running provisioner: shell... > default: Running: inline script > default: Provisioning system ... > default: Reading package lists... > default: Building dependency tree... > default: Reading state information... > default: cowsay is already the newest version. > default: unzip is already the newest version. > default: 0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded. > default: rm: > default: cannot remove ‘/usr/share/cowsay/cows/*odo*’ > default: : No such file or directory > The SSH command responded with a non-zero exit status. Vagrant > assumes that this means the command failed. The output for this command > should be in the log above. Please read the output to determine what > went wrong. > > C:\Users\Karen.Goh\VMLinux>vagrant reload > ==> default: Attempting graceful shutdown of VM... > ==> default: Checking if box 'ubuntu/trusty64' version '20190206.0.0' is > up to date... > ==> default: Clearing any previously set forwarded ports... > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Connection reset. Retrying... > default: Warning: Connection aborted. Retrying... > default: Warning: Remote connection disconnect. Retrying... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: The guest additions on this VM do not match the installed > version of > default: VirtualBox! In most cases this is fine, but in rare cases it > can > default: prevent things such as shared folders from working properly. > If you see > default: shared folder errors, please make sure the guest additions > within the > default: virtual machine match the version of VirtualBox you have > installed on > default: your host and reload your VM. > default: > default: Guest Additions Version: 4.3.36 > default: VirtualBox Version: 5.2 > ==> default: Mounting shared folders... > default: /vagrant => C:/Users/Karen.Goh/VMLinux > ==> default: Machine already provisioned. Run `vagrant provision` or use > the `--provision` > ==> default: flag to force provisioning. Provisioners marked to run always > will still run. > > C:\Users\Karen.Goh\VMLinux> > > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > IRC: #vagrant on Freenode > --- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/31c1bcf2-8fd2-45d1-8245-0109dccb92f5%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/31c1bcf2-8fd2-45d1-8245-0109dccb92f5%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Brian Cain -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CADHESCWxoCPVTPn6KxhEjodmu%2BQBoGDO4qccyccdTJcZ9zi0AA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
