I may be missing something, but isn't this what Docker is for?
http://stackoverflow.com/questions/16647069/should-i-use-vag...
11–20 of 21 posts
I may be missing something, but isn't this what Docker is for?
http://stackoverflow.com/questions/16647069/should-i-use-vag...
Just want to point out that if you're using an encrypted filesystem, vagrant up will fail if NFS is enabled. The workaround is to use rsync to maintain the synced folders, a feature introduced in Vagrant 1.5. Just use vagrant rsync-auto to keep the guest folder in sync automatically with your local folder. If you modify files within the VM (like with a bundle install that modifies your Gemfile.lock or with rails gene…
I may be missing something, but isn't this what Docker is for?
You could potentially even combine the two approaches and have a Vagrant VM with a small Ubuntu stack that has docker installed and then have a set of docker containers, one per component or service.
That said, the Docker abuse setup is fairly common. I'm in the process of doing one myself right now. :)
One thing that's bitten me a few times is case-sensitivity when using NFS and HFS+ -- still wishing I could find a solution that didn't require setting up an additional partition on my host machine.
The one thing that became a problem was managing vmware (the plugin is a closed source one, so it was hard to debug any issue that came up with it - easily solved by writing our own open source one)
This is pretty much what I do when developing as it's a good idea to make your dev environment as close to production as possible. I do however substitute chef for ansible as I found chef difficult to use on a single server (chef-solo was flakey) and bootstrapping is a pain. For writing anisble playbooks to use with Vagrant I found the following post very useful - http://hakunin.com/six-ansible-practices
I found "Taste Test"[1] by Matt Jaynes to be a nice and quick (if slightly expensive) comparison between the various configuration managers.
[1]https://devopsu.com/books/taste-test-puppet-chef-salt-stack-...
I tried using Vagrant on my company Macbook but found it much slower than just running everything on OSX. Does anyone have any tips for improving the performance?
This is pretty much what I do when developing as it's a good idea to make your dev environment as close to production as possible. I do however substitute chef for ansible as I found chef difficult to use on a single server (chef-solo was flakey) and bootstrapping is a pain. For writing anisble playbooks to use with Vagrant I found the following post very useful - http://hakunin.com/six-ansible-practices
While I'd favor using proper config management this was a much better use of my time.