3 ms·
No this isn't Docker speaking. This is me. I've always felt that Vagrant was a solution in search of a problem and no being at Docker hasn't changed that eithe
by huslage 11y ago
No this isn't Docker speaking. This is me.
I've always felt that Vagrant was a solution in search of a problem and no being at Docker hasn't changed that either way. I have colleagues that love Vagrant and they are certainly entitled to that opinion, as much as I'm entitled to think that it's horrible.
I honestly haven't seen any value brought from Vagrant or its ilk to anyone. There is temporary relief from some very real problems of transmitting development environments around the place. But the tool ends up creating pets that you have to care for over long periods of time. You have to deal with entire operating systems when you really want to abstract away the OS in favor of getting some real work done.
Configuration files as infrastructure aren't particularly interesting to me. I don't see how building annoying bits of configuration will fix anything in the long run.
Also note that while I think the HashiCorp infrastructure-as-code attempts are quite lacking, their Consul and Vault tools are really nice. :)
- rubiquity 11y ago> Configuration files as infrastructure aren't particularly interesting to me. How is this any different than a Dockerfile? Vagrantfile is certainly more abstract I guess.