does running VMs under the top of Vagrant consume more overheads in terms of Hardware resources like RAM, CPU usage, etc?.. is there any more benefit than just what you explained in this video...
Vagrant lowers development environment setup time, increases production parity, and makes the "works on my machine" excuse a relic of the past. But, yes, it increases the load on single hardware. Though this can be eliminated by a few techniques. Here are some reasons I've seen for using Vagrant over just VirtualBox. 1. Set Up Multi-VM Networks with Ease Most of the Vagrant power-user content I've read has been about setting up multiple VMs at the same time. Vagrant gives you a single config file to set these up, enabling you to launch all of them with one command. Say you've configured three VMs to network with each other using static IPs on the 192.168.1.* subnet. You find yourself in a location that is already using that subnet to hand out IP addresses, and your VMs now conflict. With Vagrant, you can simply edit the Vagrantfile and reload the VMs, whereas with VirtualBox you'd have to open the settings for each VM, if not boot each VM and change them inside. 2. Source Control By putting the settings in a text file, it enables the configuration to be put under source control. Made some changes last week and accidentally broke the image? Just revert the changes and reload the VM. You can accomplish this with VirtualBox snapshots, but it will take up much more space than just a Vagrantfile. 3. Various Platforms There's a large number of boxes available at sites such as vagrantbox.es. This enables you to try various OSes or distributions, applying the same provisioning to set up similar environments. This can help with testing or adding support to new platforms, and would be time-consuming using just VirtualBox. Source/Credits - superuser.com/questions/584100/why-should-i-use-vagrant-instead-of-just-virtualbox
Thanks for the question, Satyaarth. The short answer is that if you want to manage machines, you should use Vagrant. And if you want to build and run applications environments, you should use Docker. Vagrant is a tool for managing virtual machines. Docker is a tool for building and deploying applications by packaging them into lightweight containers. A container can hold pretty much any software component along with its dependencies (executables, libraries, configuration files, etc.), and execute it in a guaranteed and repeatable runtime environment. This makes it very easy to build your app once and deploy it anywhere - on your laptop for testing, then on different servers for live deployment, etc. Credit - Stack Overflow (Solomon Hykes)
does running VMs under the top of Vagrant consume more overheads in terms of Hardware resources like RAM, CPU usage, etc?.. is there any more benefit than just what you explained in this video...
Vagrant lowers development environment setup time, increases production parity, and makes the "works on my machine" excuse a relic of the past.
But, yes, it increases the load on single hardware. Though this can be eliminated by a few techniques.
Here are some reasons I've seen for using Vagrant over just VirtualBox.
1. Set Up Multi-VM Networks with Ease
Most of the Vagrant power-user content I've read has been about setting up multiple VMs at the same time. Vagrant gives you a single config file to set these up, enabling you to launch all of them with one command.
Say you've configured three VMs to network with each other using static IPs on the 192.168.1.* subnet. You find yourself in a location that is already using that subnet to hand out IP addresses, and your VMs now conflict. With Vagrant, you can simply edit the Vagrantfile and reload the VMs, whereas with VirtualBox you'd have to open the settings for each VM, if not boot each VM and change them inside.
2. Source Control
By putting the settings in a text file, it enables the configuration to be put under source control. Made some changes last week and accidentally broke the image? Just revert the changes and reload the VM. You can accomplish this with VirtualBox snapshots, but it will take up much more space than just a Vagrantfile.
3. Various Platforms
There's a large number of boxes available at sites such as vagrantbox.es. This enables you to try various OSes or distributions, applying the same provisioning to set up similar environments. This can help with testing or adding support to new platforms, and would be time-consuming using just VirtualBox.
Source/Credits - superuser.com/questions/584100/why-should-i-use-vagrant-instead-of-just-virtualbox
Hi, is vagrant is useful in 2023 now? does it have any future?
Not that much to be honest. But, for practicing personal projects and POCs, it's indeed a great tool.
@@LogicOpsLab Thanks for the quick answer !
@@sachintak9600 You're welcome 🙂
Wow! Great explanation!
Means a lot!
Thanks Soo much, appreciate the effort
Means a lot!
Thanks 🙏
You're welcome 🙏🏻
what is the diff bw vagrant and docker
Thanks for the question, Satyaarth. The short answer is that if you want to manage machines, you should use Vagrant. And if you want to build and run applications environments, you should use Docker.
Vagrant is a tool for managing virtual machines. Docker is a tool for building and deploying applications by packaging them into lightweight containers.
A container can hold pretty much any software component along with its dependencies (executables, libraries, configuration files, etc.), and execute it in a guaranteed and repeatable runtime environment. This makes it very easy to build your app once and deploy it anywhere - on your laptop for testing, then on different servers for live deployment, etc.
Credit - Stack Overflow (Solomon Hykes)