Hi & Thanks Alvaro, when I run the vagrant box list
I can see below boxes
*$ vagrant box list*
laravel/homestead (virtualbox, 0.2.7)
laravel/homestead (virtualbox, 0.3.0)
laravel/homestead (virtualbox, 0.4.2)
scotch/box (virtualbox, 3.0)
*scotch/box (virtualbox, 3.5)*
*$ vagrant global-status*
id name provider state directory
------------------------------------------------------------------------
*0376f86* default virtualbox running F:/october-demo
As you can see above the server id 0376f86 is the same server which is
*scotch/box
(virtualbox, 3.5) *and I'm not sure how to switch to scotch/box
(virtualbox, 3.0)
My vagrant up out is as follow
*$ vagrant up*
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'scotch/box' version '3.5' 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: Adapter 2: hostonly
==> 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: 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: 5.1.21
default: VirtualBox Version: 5.2
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
default: /var/www => F:/october-demo
==> default: Machine already provisioned. Run `vagrant provision` or use
the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always
will still run.
Let me know if it makes any sense and you can help further.
Kind regards,
Adil
On Sunday, 30 June 2019 19:49:13 UTC+5, Alvaro Miranda Aguilera wrote:
>
> hello
>
> Are 2 separate things here.
>
> Templates and running VMs.
>
> Templates or vagrant boxes is from where a running VM will be created.
>
> vagrant box list
>
> will show vagrant boxes or templates.
>
>
>
> A total separate thing is running VMs.
>
> vagrant global-status
>
> this will display the running VMs and the directory from where it got
> started.
>
> If you upgrade a base box, and you want to upgrade the running VM, please
> be aware that the process involve manually running the commands.
>
> vagrant destroy
> vagrant up
>
>
> If you haven't run vagrant destroy, then the running VM should be listed
> in the output of
>
> vagrant global-status
>
> from there you could do
>
> vagrant ssh <id>
>
> and connect to the VM.
>
> Alvaro.
>
>
> On Sun, Jun 30, 2019 at 9:49 AM Adil Shahzad <[email protected]
> <javascript:>> wrote:
>
>> Hi everyone!
>> I recently upgraded my VAGRANT to 2.2.5 version and I've the attached
>> boxes. I was running scotchbox 3.0 and decided to add the latest box
>> 3.5, as soon as I added 3.5 I lost my DB's and can't find them. I can see
>> my previous scotch and I've the screen shot attached. I'm not sure how to
>> revert back to that version and may be if i can get my db's back? Any help
>> will be much appreciated.
>>
>> Kind regards,
>> Adil
>>
>> --
>> 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] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vagrant-up/afe7aa62-0730-4add-8b37-305b72acd436%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/vagrant-up/afe7aa62-0730-4add-8b37-305b72acd436%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Alvaro
>
>
--
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/e90db7b0-b5bb-48c1-a382-9881d6d5f0be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
