vagrant-hostmanager icon indicating copy to clipboard operation
vagrant-hostmanager copied to clipboard

:pencil: A Vagrant plugin that manages hosts files within a multi-machine environment.

Results 82 vagrant-hostmanager issues
Sort by recently updated
recently updated
newest added
trafficstars

Thanks for your nice project, it is very useful. This is not a issue, but a request. I'm running Vagrant 1.8.1 on Fedora Workstation 24, to install vagrant-hostmanager 1.8.3 on...

We have separate hostmanager configuration stanzas for different Providers; right now, if you set a hostmanager config on a provider's override block, it is completely ignored. This patch fixes it....

Vagrant: 1.7.2 Hostmanager: 1.6.0 Provider: Virtualbox 4.3.30 Host OS: OSX 10.9.5 Guest OS: Ubuntu 14.04 --- On `vagrant up`, the hostfile entries are created on both host and guest, but...

enhancement - best practice

Have you considered copying the `/.vagrant.d/tmp/hosts.local` file to `/tmp` first so that the Passwordless sudo instructions don't change per user?

more information needed

If `hosts.local` is served via NFS with `root_squash` enabled then root cannot access the file and the line `sudo cp #{file} #{hosts_location}` fails with `cp: cannot stat: Permission denied`.

Wondering if it’s possible to make vagrant-hostmanager play nicely with a multi-machine config, i.e. something like the form: ``` Vagrant.configure('2') do |config| config.vm.define "default", primary: true do |default| default.vm.hostname =...

help wanted

Apologies if this is puphpet specific, but I thought it would be worth posting an issue here as well in case the problem is on the plugin end! https://github.com/puphpet/puphpet/issues/2186

more information needed

Hostmanager can only deal with one provider at a time. If you `vagrant up` a virtualbox vm, then an aws, all information of your virtualbox vm will be removed from...

When overwriting /etc/hosts the owner is set to vagrant and the selinux permissions are lost causing various services to fail. Below is the quick fix workaround: [vagrant@centos65 var]$ sudo ls...

more information needed

By setting hostmanager.disabled inside a config.vm.define block.

enhancement - nice-to-have