You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 25, 2023. It is now read-only.
In a Vagrantfile config, the Vagrant hostnames given by config.vm.define are ignored and landrush tries to rename the host to the same thing for each instance. Instead, it's using the current folder's name?
E.g. I get:
$ vagrant up --provider=libvirt
...
==> h1: Creating image (snapshot of base box volume).
==> h2: Creating image (snapshot of base box volume).
...
==> h1: [landrush] adding machine entry: dev-cluster.vagrant.test => 192.168.121.20
==> h2: [landrush] adding machine entry: dev-cluster.vagrant.test => 192.168.121.133
In a Vagrantfile config, the Vagrant hostnames given by
config.vm.define
are ignored and landrush tries to rename the host to the same thing for each instance. Instead, it's using the current folder's name?E.g. I get:
Using a config like
I'd expect h1.vagrant.test and h2.vagrant.test, not dev-cluster.vagrant.test
The text was updated successfully, but these errors were encountered: