4 ms·
From personal experience, I use docker-compose to create most development environments today. The main reason for this is that maintaining a vagrant (base) box
by trey-jones 9y ago
From personal experience, I use docker-compose to create most development environments today. The main reason for this is that maintaining a vagrant (base) box is cumbersome, while maintaining a Dockerfile and/or a docker-compose file is not.
However, there are still cases that I think Vagrant is far superior. I recently had a security-related use-case that wanted me to very precisely replicate a common production environement (LAMP w/ exim4 MTA). On docker this is complicated. On Vagrant it's very simple.
So I don't think it's dead or dated, even though Docker has replaced it for a large range of my own use cases.
- stephenr 9y agoIs there some specific reason you would maintain your own base box? My company maintains a series of Debian base boxes (forked from the box cutter project) but our bread and butter is infra projects, and packer makes it a pretty quick process to rebuild once you identify what to change for a given fix/feature.