Things I Wish I'd Known Before Using Vagrant

304 点作者 zwischenzug超过 7 年前

29 条评论

scrollaway超过 7 年前

Here's what I wish I'd known before using Vagrant:1. How to properly do cross-platform, high-performance two-way synced folders between host and guest. Most providers only support one-way syncing. Virtualbox has shared folders, but their performance is pretty lousy and they have issues with relative symlinks. In fact, I still don't fully know what the correct setup is for a dev environment where the files are edited on the host and the guest immediately picks up on them...2. This idea that with vagrant you'll never again say "It works on my machine" is a lie. So many inconsistencies between Vagrant on Windows, Linux and macOS. Internet connection sharing, line endings issues, symlinking issues, ...If anyone wants to see how we're using Vagrant:<a href="https://github.com/hearthsim/hearthsim-vagrant" rel="nofollow">https://github.com/hearthsim/hearthsim-vagrant</a>I don't want to make it sound like Vagrant isn't solving a real problem though, it is. It's just not the unicorn it claims to be.

评论 #15569530 未加载

评论 #15571722 未加载

评论 #15567885 未加载

评论 #15567417 未加载

评论 #15571749 未加载

评论 #15568012 未加载

评论 #15568034 未加载

评论 #15570879 未加载

评论 #15575556 未加载

评论 #15567593 未加载

评论 #15569294 未加载

wildpeaks超过 7 年前

A couple more for the list:11. Shared folders get setup before provision scripts are run12. You can detect provision has already run (<a href="https://github.com/hashicorp/vagrant/issues/936#issuecomment-288063253" rel="nofollow">https://github.com/hashicorp/vagrant/issues/936#issuecomment...</a>) using:<pre><code> if File.exist?(".vagrant/machines/YOUR_BOX_ID/virtualbox/action_provision") </code></pre> 13. Vagrantfile configs are actually Ruby scripts, so you could do things like storing your box configs in JSON (like I did in <a href="https://github.com/wildpeaks/boilerplate-vagrant-xenial64" rel="nofollow">https://github.com/wildpeaks/boilerplate-vagrant-xenial64</a> ) instead of hardcoding them in the Vagrantfile.14. Virtualbox needs Hyper-V disabled whereas Docker for Windows requires Hyper-V enabled.

评论 #15568753 未加载

评论 #15567989 未加载

评论 #15567619 未加载

corford超过 7 年前

One thing thing I can add to this that was driving me nuts (though not strictly Vagrant's fault):The DHCP client on Ubuntu 16.04LTS doesn't always play nice with multi NIC vagrant machines. All my vagrant boxes are dual NIC (eth0 is the standard 10.0.2.x NAT interface and eth1 is a private interface in the 192.168.56.x range with a static IP - which makes it easier for various vagrant machines to talk directly to each other).I had an infuriating issue where my boxes would startup and then randomly (it seemed at the time) stop responding to network requests. Initially I thought they were hanging for some reason and would tear them down and re-init them.Finally thought to enable GUI mode and I noticed that even though a box had stopped responding, I could login fine via the virtual box GUI.It turned out that Ubuntu's DHCP client was ignoring /etc/network/interfaces (auto generated by vagrant) and wrongly refreshing IP leases on both interfaces (eth0 and eth1).The trick is to kill the running dhclient during provisioning and restart it with switches that force it to only maintain leases for eth0:<pre><code> machine.vm.provision "shell", inline: "kill $(pidof dhclient) && /sbin/dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -I -df /var/lib/dhcp/dhclient6.eth0.leases eth0"</code></pre>

评论 #15567404 未加载

评论 #15567346 未加载

therealmarv超过 7 年前

I wished I'd known that Vagrant + Windows is always full of surprises. So many problems with Windows developers because Vagrant will not work as expected there :(Anybody know any best practices what to do with Windows developers? I'm thinking of going to docker... but I'm not sure if this really helps.

评论 #15567377 未加载

评论 #15567492 未加载

评论 #15567591 未加载

评论 #15571437 未加载

评论 #15567298 未加载

glenscott1超过 7 年前

If you work with other developers and store your Vagrantfile in source control, then you can allow per-developer settings using the method shown here: <a href="https://www.glenscott.co.uk/blog/allow-per-developer-vagrantfile-customisations/" rel="nofollow">https://www.glenscott.co.uk/blog/allow-per-developer-vagrant...</a>

评论 #15568058 未加载

bauerd超过 7 年前

I was a long-time Vagrant user but recently switched almost completely to Docker (Compose). What features does Docker miss that make people keep using Vagrant?

评论 #15569452 未加载

评论 #15568750 未加载

评论 #15568786 未加载

评论 #15568582 未加载

评论 #15571029 未加载

评论 #15569085 未加载

评论 #15569738 未加载

评论 #15568529 未加载

评论 #15568853 未加载

conradfr超过 7 年前

If you're a PHP dev (or even not) check <a href="https://puphpet.com/" rel="nofollow">https://puphpet.com/</a>I generate my Vagrant files for all my side projects with it and it's a real time saver, especially if you're not savvy in those fancy provisioners or sysadmin in general.

drinchev超过 7 年前

Vagrant's private network is really cool as well. I use it to test ansible provisioning scripts for server infrastructure.<pre><code> config.vm.define "ums-01" do |machine| machine.vm.network "private_network", ip: "192.168.1.10" machine.vm.network :forwarded_port, guest: 22, host: 2210, id: "ssh" end config.vm.define "ums-02" do |machine| machine.vm.network "private_network", ip: "192.168.1.20" machine.vm.network :forwarded_port, guest: 22, host: 2220, id: "ssh" end </code></pre> -- <a href="https://www.vagrantup.com/docs/networking/private_network.html" rel="nofollow">https://www.vagrantup.com/docs/networking/private_network.ht...</a>

wkral超过 7 年前

I'd advise caution with the use of landrush, at my company it was very quick to get up and running using it, but we encountered several problems with it over time. We have several vagrant boxes coming up and down at various times on each developer's machine and it would tend to get out of sync in various cases, hold on to records for machines that no longer existed and macOS DNS cache also played a role.Eventually we replaced it with Dnsmasq and a static IP setup with each development box getting an immutable static IP. Dnsmasq runs on a guest VM that needs to always be up for other purposes as well.As always the effort from the landrush developers is much appreciated and it may be suitable for a limited number of boxes but it didn't scale with our usecase.

mitchty超过 7 年前

Here's my advice go to GitHub and type:filename:Vagrantfile thing you're looking forYou'd be suprised how many hidden gems are on GitHub that you can use to figure out how to use vagrant. This tip applies more generally.

评论 #15568903 未加载

invisiblea超过 7 年前

- Vagrant Triggers plugin is super useful <a href="https://github.com/emyl/vagrant-triggers" rel="nofollow">https://github.com/emyl/vagrant-triggers</a>- I've found VMware Fusion as a provider worth the extra cost/disk space

评论 #15568203 未加载

评论 #15568082 未加载

msielski超过 7 年前

Also big fan of vagrant global-status. I have it aliased to vgs in my terminal.Also very helpful for those using Vagrant on OSX is Vagrant Manager [0] which gives you menu-bar integration and a quick interface to turn VMs on and off. It's useful even to remind myself when I've left some VMs on, especially if I'm running on battery.[0] <a href="http://vagrantmanager.com/" rel="nofollow">http://vagrantmanager.com/</a>

achiang超过 7 年前

We've avoided many of the problems (and solutions) in the link by standardizing on Ubuntu laptops for the host OS, and using vagrant-lxc to run our vagrant guests.<a href="https://github.com/fgrehm/vagrant-lxc" rel="nofollow">https://github.com/fgrehm/vagrant-lxc</a>At least one or two of our new hires started with OSX hosts, but switched to Ubuntu after a while, to avoid virtualbox pain.[edit: added vagrant-lxc link]

mister_mister超过 7 年前

For me vagrant works best with declarative configuration and a runner. something like this, with sane defaults and many options available by changing fields in a dictionary.<a href="https://github.com/Attumm/vagrantfile_example/blob/master/Vagrantfile" rel="nofollow">https://github.com/Attumm/vagrantfile_example/blob/master/Va...</a>

nicolasbistolfi超过 7 年前

Fore me something that inclined me to use vagrant, was the share feature, so I can let anyone in the world check my development environment. Now they deprecated that feature and <a href="https://ngrok.com" rel="nofollow">https://ngrok.com</a> does the job very well.

pasta超过 7 年前

Ofcourse this depends on the kind of project, but my last experience with a big Laravel project was that I was running the project working under Apache on my local machine and the rest of the team was loosing a lot of time because Vagrant was not working as expected.I can understand the need for reproducible environments. But when so much time is lost I doubt the first thing you need is something like Vagrant. To me Vagrant is a tool that you use when the team starts to struggle with "works on my machine". But not before that. Because most of the time (well for PHP at least) it's very easy to make it work on all machines.

评论 #15567987 未加载

评论 #15568870 未加载

damagednoob超过 7 年前

I've used Vagrant extensively in the past but since I found docker-compose, I haven't reached for it over the past year.

评论 #15568631 未加载

jeffshek超过 7 年前

Another thing to add to the list is you can set Paravirtualization Interface if you're using VirtualBox.If your defaults are currently on "Legacy", empirically we saw 10-30% speedup by switching to "KVM".

pmontra超过 7 年前

There used to be a problem with running Vagrant on VirtualBox with more than 1 CPU: <a href="https://github.com/rdsubhas/vagrant-faster/issues/5" rel="nofollow">https://github.com/rdsubhas/vagrant-faster/issues/5</a>Explanation and workarounds: <a href="http://www.mihaimatei.com/virtualbox-performance-issues-multiple-cpu-cores/" rel="nofollow">http://www.mihaimatei.com/virtualbox-performance-issues-mult...</a>Did they fix this?

jeff_vader超过 7 年前

My top tip: install your dotfiles into any Vagrant VM without modifying anything in the VMs Vagrantfile/provisioning scripts: <a href="https://gist.github.com/tadas-s/0cd468a4cc9fa4cafce6fe57a5dce123" rel="nofollow">https://gist.github.com/tadas-s/0cd468a4cc9fa4cafce6fe57a5dc...</a>

评论 #15570507 未加载

bryanlarsen超过 7 年前

11. Virtual Box sucks. Try out alternatives, I like vagrant-lxc.

评论 #15569903 未加载

评论 #15568114 未加载

waibelp超过 7 年前

Thank you for "vagrant global-status". There's still a lot of boxes I don't even remember.

评论 #15567251 未加载

marksellers超过 7 年前

I've done development with all the databases, languages and packages installed on the host machine, as well as with vagrant. With the VM, I have to ssh in, or switch windows to run tests, whereas before I could just run the tests in vim. How do people achieve fluency with these?I suppose I could install some more of my tools on the VM, but if you take that to its absurd conclusion, I'm just running a clone of my host on the VM.It seems more useful, maybe, to just run databases and other services in the VM. Those are the more difficult bits to manage usually. A good programming language already has version and package management facilities.Or perhaps am I missing something? Anyone have another workflow?

评论 #15569522 未加载

评论 #15567497 未加载

评论 #15567499 未加载

评论 #15567514 未加载

zimbatm超过 7 年前

Another thing that's good to know: vboxfs (the default VirtualBox file-sharing filesystem) doesn't support mmap().The are quite a few software that use mmap to access files, especially databases. When that happens, either avoid using the shared folder or switch to using the nfs mount.Here is the ticket about it that's been opened 10 years ago: <a href="https://www.virtualbox.org/ticket/819" rel="nofollow">https://www.virtualbox.org/ticket/819</a>

vlunkr超过 7 年前

Adding swap really is critical. Machines running out of swap was causing my MBP to crash ~once a day, enough that I ran linux on it for a while (it was more stable for whatever reason) until we figured out what the issue was.

cwaffler超过 7 年前

I highly recommend lando. Basically an easy to use CLI wrapper for docker apps.<a href="https://docs.devwithlando.io/" rel="nofollow">https://docs.devwithlando.io/</a>

评论 #15571299 未加载

ironjunkie超过 7 年前

Is anyone really using Vagrant for anything more than quick tasks on your local dev machines? I always perceived Vagrant as a hack.

评论 #15570336 未加载

评论 #15570579 未加载

评论 #15570329 未加载

tonetheman超过 7 年前

Yup yup this is a good list. Thanks for mentioning landrush, it is something I could have used.

grabcocque超过 7 年前

Vagrant's documentation leaves something to be desired. It's perfectly possible to control many VMs from one Vagrantfile, but good luck figuring out how from the docs.I mean with a bit of ruby knowhow and some digging you can figure most stuff out, but Vagrant's documentation still lags behind Hashicorp's other stuff which is usually very well documented.

评论 #15567232 未加载