So I am using docker for the second time. Still prefer vagrant.

Those are very much not comparable tools...

Not comparable at all indeed.
Docker saves life you know, you should use it in almost all your projects x)

The real fun begins if you spin up vagrant boxes to run a docker swarm on them to then run your docker containers on the swarm.

May your CPU cooler be with you.

Vagrant and Docker serve completely different purposes. While Vagrant can run Docker containers (iirc) you're most likely using it to run VMs. VMs are (usually) a lot heavier than containers. They simply don't serve the same purpose, neither in production or development.

Docker (+compose/k8s/etc) is awfully complicated.

But when the company runs docker on CI & production, and you run vagrant locally... That means you need to maintain 2 infrastructure configurations. And then some engineer decides to upgrade the Redis version, and now your code which uses some deprecated function works locally, but not after deploying...

So usually it's easier to just run the complete docker compose config that also runs on CI & production, with a few environment flags.

Docker is kind of "the best of all terrible options".

@bittersweet why docker is terrible? I had very good experience using docker for last few years

@Angry-dev Great concept, but:

1. Typing out a docker run command can take longer than compiling Linux from scratch, and all the CLI stuff reminds me of all the git plumbing commands

2. Getting shit to actually work can take quite some effort — networks and share mounts can have odd quirks, random orphaned images filling up disk, starting on boot not working for mystery reasons, etc.

Once it works, it's all good, but getting there is STILL hard work.

Overall I'm a fan of docker, I just hate configuring infra. Even "infra as code" doesn't allow me to completely escape all the tediousness.

My only memory of using vagrant is someone handing me the setup file, telling me to run a command and having to wait 30 minutes for the thing to work. And the dependencies were all wrong.

With docker I just never got past the documentation.

@bittersweet

"1. Typing out a docker run command can take longer than compiling Linux from scratch, and all the CLI stuff reminds me of all the git plumbing commands"

Oh thats really not an issue - can always make short cut commands. Maybe even create UI?

"2. Getting shit to actually work can take quite some effort — networks and share mounts can have odd quirks, random orphaned images filling up disk, starting on boot not working for mystery reasons, etc."

Thats true. But is it possible to get same thing without effor? Probably there is no easier way.

But past few years it really all went smooth more or less. Like without dockerizing - to set up project I need to make nginx, hosts configurations. With docker - just run one short command and everything is installed.