3

Error while running vagrant

I'm new in Windows. I use Windows 10. While I run vagrant on my machine, there are some issues with UID. Please look at the picture for more information.

While I run vagrant up, I get some warning :

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 as created. Please re-run Vagrant with
that user. This is not a Vagrant issue.

The UID used to create the VM was: 1000
Your UID is: 0
Uwe Keim
  • 39,551
  • 56
  • 175
  • 291
Nicky Valentino
  • 31
  • 1
  • 3
  • I found [similar problem in Linux](http://stackoverflow.com/questions/31644222/vagrant-not-starting-up-user-that-created-vm-doesnt-match-current-user/32977467) but I didn't know how to apply that case in my Windows 10. – Nicky Valentino Apr 15 '16 at 00:51
  • Possible duplicate of [Vagrant Not Starting Up. User that created VM doesn't match current user](https://stackoverflow.com/questions/31644222/vagrant-not-starting-up-user-that-created-vm-doesnt-match-current-user) – Eugen Konkov Jun 26 '18 at 10:46

5 Answers5

8

Looks like you are logged in as sudo, hence the UID is different. Log-out of sudo and try vagrant up as normal user.

If the above doesn't work then update the below file

vi .vagrant/machines/default/virtualbox/creator_uid

to add 0 in it

Let me know if this helps.

user3805033
  • 157
  • 1
  • 3
5

Find this path and change to 0.

.vagrant/machines/default/virtualbox/creator_uid

Bala
  • 913
  • 9
  • 18
2

In the Windows folder. Vagrant is in the same folder as the Vagrantfile. As default won't be available, so you may have to edit in every vm but the path is the same: vagrant/machines/(name of the vm)/virtualbox/creator_uid

Marcs
  • 3,768
  • 5
  • 33
  • 42
Artur Licks
  • 21
  • 4
2

Remove .vagrant dir in the current working dir and re-run vagrant up command. Error, because of copy / backup of Vagranfile /s from one system to another system. user id's mismath to the Vagrant to bring up the environment.. hope it helps cheers..!! :))

siva krishna
  • 21
  • 1
0

This happened to me (on subsequent runs) when I used vagrant up with elevated privileges for the first time (administrator).

steakoverflow
  • 1,206
  • 2
  • 15
  • 24