> but I don't understand why I should go through all that effort when Vagrant Just Works™ most of the time
Problem with Vagrant is you can't take the VM you created and deploy it on any random Linux server (or random Docker-hosting cloud provider) - while a pure Docker solution can be deployed literally anywhere with Docker support, as long as you give it a way to persist the data directories of the services. docker-compose is a hit-and-miss across hosters, and you can't use it on DC/OS or Kubernetes environments.
I use my script collection mainly for dev environments, but it's useful when you want to spin up QA/dev instances without having to provision real servers.
Problem with Vagrant is you can't take the VM you created and deploy it on any random Linux server (or random Docker-hosting cloud provider) - while a pure Docker solution can be deployed literally anywhere with Docker support, as long as you give it a way to persist the data directories of the services. docker-compose is a hit-and-miss across hosters, and you can't use it on DC/OS or Kubernetes environments.
I use my script collection mainly for dev environments, but it's useful when you want to spin up QA/dev instances without having to provision real servers.