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

Question

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

Answer 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.

Answer 2

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.

Answer 3

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

Answer 4

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.

Answer 5

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.

Answer 6

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