Hello All,
My Linux development environment is Vagrant + VirtualBox on top of a Win10 
host.
In the Github app I am trying to build, it requires to create groups and 
users with group & user IDs. 
Because of the underlying layers/modules this app uses, one of the groupID 
deployed is 999. 
When I ran the "groupadd" command inside the guest Ubuntu on my above 
development platform, it returned an error saying 999 is already occupied 
by another app on my platform. This other app so happened to be “vboxsf” 
aka VirtualBox.
I can’t change the groupID of the app I am trying to build as it is too 
complicated and I don’t know it well. And I think gid=999 is likely 
associated with Postgres module this app is using.

The easiest way to solve is to change the “vboxsf” uid & gid to something 
else using command like:

sudo mount -t vboxsf folder share -o uid=1000,gid=1000

My question is, this may sound ok but it should not work. 
My thinking is the guest Ubuntu is running on Vagrant + VirtualBox. I 
cannot possibility change the default VirtualBox uid, gid within the guest 
Ubuntu. Doing this, will destroy my Vagrant + VirtualBox environment.
Am I correct?
Can anyone suggest a possible way to solve this conflicting uid+gid 
assignment problem for my Vagrant + VirtualBox setup?
Thanks in advance.

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/d1a9d508-8f09-4ba8-9393-1d0baad40b85%40googlegroups.com.

Reply via email to