Skip to content
This repository has been 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

Open
stephaneerard opened this issue Dec 29, 2018 · 1 comment
Open

The VirtualBox VM was created with a user that doesn't match #341

stephaneerard opened this issue Dec 29, 2018 · 1 comment

Comments

@stephaneerard
Copy link

$ 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.
@hferentschik
Copy link
Contributor

Can you share your full Vagrantfile? Which box are you using? It might also help to see more of the boot messages.

@hferentschik hferentschik changed the title "The VirtualBox VM was created with a user that doesn't match" The VirtualBox VM was created with a user that doesn't match Feb 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants