vagrantfile - How to specify a provider during `vagrant up` command? - Stack Overflow
docker - What is the difference between a Vagrant Provider and a Vagrant Provisioner? - Stack Overflow
New list-providers command
Provider for UTM (VM for M1 processors)
Videos
Factsheet
This is a current limitation of vagrant
you cannot back the same machine with both VirtualBox and VMware Fusion. This is a limitation that will be removed in a future version of Vagrant.
I am not sure if it will get ever solved by vagrant. but so you have created your machine once with virtualbox so now it is expected you work with this VM, not with another machine.
One way to fix this is to backup the .vagrant folder with the reference of the existing VM like (.vagrant.vbox) and re-run vagrant up --provider parallels to let it create the parallels VM.
If you want to switch back to the virtualbox VM, you can backup the newly created .vagrant folder and rename the .vagrant.vbox as .vagrant
Short answer
Remove the .vagrant folder in the project.
rm -r .vagrant
(I leave this duplicated answer because I personally was too lazy to read the previous one and missed the solution)
The underlying virtualization solutions are called providers. To work with Vagrant, you have to install at least one provider (e.g. Virtualbox, VMWare)
Provisioning in Vagrant is the process of automatic installation and configuration of the system within during
$ vagrant upand the tools to perform this operation are called provisioners (e.g. Shell scripts, Chef, Puppet).
Provider vs Provisioner
Vagrant uses Providers such as hypervisors (e.g VirtualBox, Hyper-V) or Docker to create and run virtual environments. Vagrant uses Provisioners (e.g Ansible, Puppet, Chef) as configuration tools to customize these environments, e.g carrying out installs and starting apps.
How does Docker fit in?
If a hypervisor is used as a Provider, the environment that is created is a virtual machine based on a self-contained image of an operating system environment as provided by a “Vagrantbox” (aka “box”). The box is utilized by Vagrant to create a dedicated kernel and set of operating system processes for the virtual machine.
If Docker is used as a Provider and Docker is available on the host system, Vagrant manages and runs containers directly on the host system. Here Vagrant is not actually building and managing a virtual machine but rather is working with the Docker engine running on the host to manage and build Docker containers.
source: https://en.wikipedia.org/wiki/Vagrant_(software)
-
formerly open-source?
-
formerly software product?
-
formerly active?
What does it mean by "formerly"?
Edit 1:
Here's the entire paragraph just in case:
Vagrant is a formerly open-source software product for building and maintaining portable virtual software development environments;[5] e.g., for VirtualBox, KVM, Hyper-V, Docker containers, VMware, Parallels, and AWS. It tries to simplify the software configuration management of virtualization in order to increase development productivity. Vagrant is written in the Ruby language, but its ecosystem supports development in a few other languages.
Edit 2:
Answer
formerly open-source
ref: "HashiCorp adopts Business Source License" AUG 10 2023 https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license
Thanks to kind redditors.
btw looks like not only for Vagrant, but also Terraform and maybe other their products as well.