This repository was archived by the owner on Jun 25, 2023. It is now read-only.
This repository was archived by the owner on Jun 25, 2023. It is now read-only.
The VirtualBox VM was created with a user that doesn't match #341
Description
$ vagrant --version
Vagrant 2.2.2
VirtualBox 6.0.0 + ext pack.
Windows 10 Pro host.
$ vagrant plugin install landrush
Installing the 'landrush' plugin. This can take a few minutes...
Fetching: filelock-1.1.1.gem (100%)
Fetching: landrush-ip-0.2.5.gem (100%)
Fetching: eventmachine-1.0.9.1.gem (100%)
Building native extensions. This could take a while...
Fetching: rubydns-0.8.5.gem (100%)
Fetching: win32-process-0.8.3.gem (100%)
Fetching: landrush-1.3.1.gem (100%)
Installed the plugin 'landrush (1.3.1)'!
Vagrantfile for apt machine:
config.landrush.enabled = true
config.landrush.host 'apt.beable.lan', '192.168.54.4'
$ vagrant up apt
The VirtualBox VM was created with a user that doesn't match the
current user running Vagrant. VirtualBox requires that the same user
be used to manage the VM that was created. Please re-run Vagrant with
that user. This is not a Vagrant issue.
The UID used to create the VM was: 0
Your UID is: 1001
```
The ```apt``` vm was working before.
After uninstalling landrush and removing all landrush related things in Vagrantfile, ```vagrant up apt``` works back.