Docker vs Vagrant for local development?

Question

Web development

I master virtualization and asked some questions. Before that, I used a vagrant (homestead). All hosts were spinning on one virtual machine usually. But then I started to study docker, it is very difficult, but I feel the possibilities are very cool, because docker is a wonderful file sharing service . As I understand it, the main feature is that I can set up the configuration and then run the project absolutely anywhere without setting up the environment. docker to make it portable? Or is vagrant still more convenient and easier for local development?

Answer 1

It is correct to talk about comparing vagrant and docker-compose. If you have production completely through docker, then you definitely need to use docker-compose, if not, then it can be different. In any case, it is easier to start with a vagrant, and more useful. So I recommend.
ps On Hexlet, we wrote a lot of guides, including about docker, vagrant, virtualization and all that: guides.hexlet.io It will be useful for beginners.

Answer 2

These are different technologies for different purposes.
If your application was developed to work inside containers (for kubernetes, for example), then of course it is better to use docker compose.
But not every application was developed this way, some of them cannot be put into docker without ugly crutches, especially if there are a lot of violations of the principles of 12 factors .
And then it turns out to be more convenient to use vagrant, but the meaning is the same: a portable customized environment, one thing per project.
Laravel Homestead kills the whole point of vagrant (independence of runtime environments, storing runtime settings along with the project - all this is not there). Apparently, the developers of Laravel wanted to hype on a buzzword, but could not figure out the technology.