Closed iocouto closed 2 years ago
The /vagrant
folder being present in a box is not required since it's just an arbitrary path. Creating that folder is handled by Vagrant itself when something tries to mount there.
@timschumi
I feel like you missed the essence of the issue. /vagrant isn't being mounted - I'm seeing the same thing. On VMware, so it's not VirtualBox specific
I have tested this on libvirt and VirtualBox, and everything seems to work as expected.
After creating a new Vagrantfile, no folder and no mount is present.
After you add the shared folder to the Vagrantfile, the folder gets created automatically and the directory from the host is mounted inside.
Might be VMware specific then. But then I don't know what the original person who opened the ticket did wrong, since they are using virtualbox.
I have since resolved my problem, one needs to manually pass enableSharedFolders (once) to the VM with a VMware cli tool, since the vagrant VMware plugin fails to do so
On Sat, Oct 9, 2021, 3:55 PM Tim Schumacher @.***> wrote:
I have tested this on libvirt and VirtualBox, and everything seems to work as expected.
After creating a new Vagrantfile, no folder and no mount is present.
After you add the shared folder to the Vagrantfile, the folder gets created automatically and the directory from the host is mounted inside.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/lavabit/robox/issues/190#issuecomment-939301359, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABVHKBBK4RH5MZLJWNKJADUGBCWJANCNFSM4Y5JY5MQ .
Looks like the problem has been fixed. Closing.
The standard
/vagrant
sync shared folder is not setup for Arch Linux - neither when using the generic/arch nor roboxes/arch, on VirtualBox.No 'vagrant' folder...
For comparison, using archlinux/archlinux: