Vagrant Not Starting Up. User that created VM doesn't match current user

vagrant virtual-machine virtualbox virtualenv
Luke picture Luke · Jul 27, 2015 · Viewed 63.1k times · Source

I was trying to start up my vagrant machine, so I navigated to the folder where my vagrantfile is, and used:

vagrant up && vagrant ssh

but I got the following error message:

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: 501

I also tried with sudo, but that didn't work either.

Do I need to switch UID's? And how would I do this?

Answer

Fred picture Fred · Aug 27, 2015

I ran into the same problem today.
I edited my UID by opening the file .vagrant/machines/default/virtualbox/creator_uid and changing the 501 to a 0.

After I saved the file, the command vagrant up worked like a champ.

NB: the .vagrant folder is in the same directory as your Vagrantfile, where you ran vagrant up

Related questions

SSH to Vagrant box in Windows?

I'm using Vagrant to start a VirtualBox VM in windows. In other platforms, I can just $ vagrant ssh to connect to the VM. How do i connect to this Vagrant box in windows? The way suggested in Vagrant documentation to …

Read More
Where does Vagrant download its .box files to?

What happens to the .box file after the following command is executed? vagrant box add lucid32 http://files.vagrantup.com/lucid32.box I can't find the lucid32.box file on the file system after download has completed.

Read More
VBoxManage: error: Failed to create the host-only adapter

I am running vagrant 1.4 and virtual box 4.3 on fedora 17 machine. When I do "vagrant up", I get this error: Bringing machine 'default' up with 'virtualbox' provider... [default] Clearing any previously set forwarded ports... [default] Clearing any previously set network interfaces... …

Read More