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

F

17

135

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?

Freefloating answered 27/7, 2015 at 2:43 Comment(0)

T

268

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

Tombolo answered 27/8, 2015 at 18:25 Comment(11)

I found myself in the same situation, I had tar up a tarball from an ubuntu machine. So simply removing the rm -rf .vagrant dir that got created in ubuntu also resolved the issue. – Lewes 4/9, 2015 at 16:49

// , Wow, thanks, @Fred! Stackoverflow serves us at its best with this kind of precise, difficult to find solution from someone who has had to deal with it before. Where will I usually find the .vagrant folder on Unix based machines? – Panthea 30/11, 2015 at 23:2

Not sure, @Nathan. Can you run a locate command for the creator_uid file? Try "locate creator_uid" at the command line to find the path to the file to edit. – Tombolo 1/12, 2015 at 19:13

// , That worked. I use my CEntOS box from ~/vagrant/centos/. It looks like the creator_uid file was at ~/vagrant/centos/.vagrant/machines/default/virtualbox/creator_uid. This seems to mean that the .vagrant in this answer usually has the same directory as the Vagrantfile for the problem machine. – Panthea 1/12, 2015 at 20:34

In my case, the creator_uid contained "90210", but my UID is 502. Rather than change the UID in the file to 0 as this solution suggested, I changed it to 502. Worked well. – Amalbergas 13/1, 2016 at 21:51

Thanks! I created a VM on my Mac, and then had my machine cloned to a new Mac. Everything about the system (other than the improved hardware) behaved the same, as far as I can tell, until I ran into this. Apparently my UID changed from 510 to 502. – Mertens 7/9, 2016 at 22:0

@NathanBasanese .vagrant folder is at the same location you ran vagrant up – Pestalozzi 10/2, 2017 at 14:17

Why can't I find the "creator_uid" file in the given directory? – Bal 21/6, 2017 at 13:52

Remove simply .vagrant at the root of your Vagrantfile – Stewardson 22/9, 2017 at 11:40

I worked I had same issue just made change in creatoruid file – Tamatamable 21/4, 2018 at 7:29

It worked, although my vagrant file was at .vagrant/machines/dev/virtualbox/creator_uid – Ry 27/6, 2018 at 15:21

S

37

Ran into this problem in a slightly different situation. The issue was that ".vagrant" was checked into the git repo, and the committer was running under a different UID than I was.

Solution: add .vagrant to .gitignore.

Stadler answered 6/10, 2015 at 18:50 Comment(2)

This was the issue I faced; however, simply adding .vagrant to .gitignore will not solve the issue - YMMV, but git rm -rf .vagrant should be run too. – Seamy 14/11, 2015 at 2:49

@marco: You're absolutely right. if ".vagrant" was added to the repo, adding it to .gitignore afterwards is too late :) – Stadler 18/11, 2015 at 0:37

U

8

I tried changing the id in .vagrant\machines\default\virtualbox\creator_uid and that did not work for me but deleting the file, creator_uid did the trick.

Umiak answered 21/1, 2016 at 21:8 Comment(0)

P

8

I ran into the same issue, but in my case it was because I had ran vagrant up under sudo, and when I came back to it later I'd forgotten.

Silly mistake, but I'm sure it's not the first time it's happened someone :)

Potful answered 16/2, 2016 at 14:43 Comment(2)

Same issue here, forgot to run under sudo. But the error message is not very indicative of that unfortunately. – Precision 10/4, 2016 at 20:39

Same here. Used sudo vagrant up but then used vagrant ssh which threw the different user error. Forgot to use sudo vagrnt ssh which worked fine. – Octet 12/2, 2021 at 22:47

A

4

just change user ID here .vagrant/machines/default/virtualbox/creator_uid

Ascribe answered 9/9, 2017 at 8:31 Comment(0)

S

2

It's possible you ran the command: sudo vagrant up

This would mean as your regular user you are unable to see or even delete the /.vagrant folder and files.

If so, simply run: sudo vagrant destroy -f

Then you should be able to run (as your normal user account): vagrant up

Scandalize answered 4/5, 2017 at 14:34 Comment(0)

A

1

According to the VirtualBox User Manual:

As a security measure, the Linux implementation of internal networking only allows VMs running under the same user ID to establish an internal network.

In other words, you have to switch to root (UID 0) to run it.

Aruwimi answered 27/7, 2015 at 2:53 Comment(1)

Shouldn't run as sudo, just delete your .vagrant directory and run as your user – Jetty 24/10, 2015 at 18:19

D

1

Run the following commands:

bash
sudo vagrant up

Donahue answered 15/6, 2016 at 0:31 Comment(0)

S

1

I faced the same problem. I deleted in .vagrant directory inside the directory where Vagrantfile was present. Then it worked.

Strophe answered 17/11, 2022 at 4:41 Comment(0)

R

0

I had the same problem after I got a new computer. Instead of of copying all files from my old computer, I had to check out the vagrant projects again from the git repository. After that, vagrant up worked fine.

Ramayana answered 25/1, 2017 at 8:38 Comment(0)

C

0

Just to add on to Fred's https://mcmap.net/q/167017/-vagrant-not-starting-up-user-that-created-vm-doesn-39-t-match-current-user answer.

Make sure you changed the correct VM's machine. For example, my VM name is NOT default but rather called homestead-7.

So the path to the correct one is:

.vagrant/machines/homestead-7/virtualbox/creator_uid

and not:

.vagrant/machines/default/virtualbox/creator_uid

This error happened to me when I changed my Mac to another Mac.

Crasis answered 19/9, 2017 at 3:16 Comment(0)

M

0

Remove the content of .vagrant hidden 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..!! :)) if u don't wish to delete that folder u can update uid of current user in file in the hidden dir of current working dir, i.e .vagrant/machines/jenkins/virtualbox$ vim creator_uid

Mayle answered 23/10, 2017 at 12:3 Comment(0)

G

0

I've faced the same situation, but I have a multi-machine Vagrantfile.

To replace the old uid (1001) by the new one (1000) I've used the following command:

for i in $(find . -type f -iname "creator_uid" ) ; do echo 1000 > $i ; done

Gaily answered 19/11, 2018 at 17:49 Comment(0)

G

0

I had the same problem I had forgotten to place sudo before vagrant up, you just have to execute sudo vagrant up in the folder of your vagrant file.

Glenoid answered 8/12, 2018 at 23:31 Comment(0)

N

0

I have Multi-Machine vagrant file. I have checked the creator_uid and it is 0 but still unable to load. So I have deleted creator_uid file for all the Multi-Machine and it worked. Path should be .vagrant\machines\<machine_name>\virtualbox

Nidia answered 10/5, 2020 at 3:27 Comment(0)

T

0

I encountered the same issue but it's because I cloned an exercise file from a GitHub repo. I found the issue being the .vagrant file included in the repository.

What worked for me is deleting the .vagrant directory and rerun vagrant up

Tereus answered 30/10, 2021 at 3:58 Comment(0)

S

-2

rm -rf .vagrant/machines/default/creator_uid

Snuffer answered 4/12, 2021 at 12:47 Comment(1)

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center. – Dogmatism 4/12, 2021 at 14:54

Recommended topics

Hot tags