Not sure where shared folders are?

[gregelin]

On vagrant, I often took advantage of /vagrant as a shared folder. That folder does not seem to be created by default in vbkick. I'm sure setting up a share folder is supported considering all the other features.

It's nice to have a share folder created by default. Even after running vbkick export it isn't clear.

[gregelin]

Guessing this problem was because guest additions were not being installed in the definition.cfg file. So closing this issue.

[wilas]

My response to this question - may be useful to someone:

Installed virtualbox gest additions are required to use shared folders. For the CentOS6 template you can just run vbkick update VM_NAME or vbkick postinstall VM_NAME - in both cases postinstall/virtualbox.sh script will be executed.

After that shared folders should be automatically mounted in your VM:

$ df -h
Filesystem      Size  Used Avail Use% Mounted on
vbkick          10G  1G   9G  10% /media/sf_vbkick

To check whether virtualbox additions are installed you can run (if you are using template):

$ vbkick validate VM_NAME
Virtualbox Guest Additions: OK
...

By default this settings are used to configure shared folders (you can change this in the definition file): shared_folders=("vbkick:%PWD%:automount")

If you want mount shared folders as /vagrant something like this must be done inside the VM:

mount #check the share name -e.g. vbkick
sudo umount vbkick
sudo mkdir -p /vagrant
sudo chown vagrant:vagrant /vagrant
id vagrant #check uid and gid numbers
sudo mount -t vboxsf -o rw,uid=500,gid=500 vbkick /vagrant/

You may want automate this process by creating postinstall/vagrant_sharefs.sh script or something similar and updating related entries in the definition file (or postinstall/adm_conxtext... if you are using that approach). The current templates don't do this because they just implement the minimum needed to export templates as a vagrant base boxes.

Advance example with shared folder is available here: https://github.com/wilas/vbkick-templates-forge/blob/master/Mer/definition-mersdk.cfg

To find more about shared folder options, please follow: https://www.virtualbox.org/manual/ch04.html#sharedfolders

NB: there is a bug in virtualbox v4.3.10 - https://www.virtualbox.org/ticket/12879 where the extra step is required to mount shared folder under custom location.

[gregelin]

+1

Greg Elin P: 917-304-3488 E: gregelin@gitmachines.com

Sent from my iPhone

On Jun 2, 2014, at 2:12 PM, Kamil Wilas notifications@github.com wrote:

My response to this question - may be useful to someone:

Installed virtualbox gest additions are required to use shared folders. For the CentOS6 template you can just run vbkick update VM_NAME or vbkick postinstall VM_NAME - in both cases postinstall/virtualbox.sh script will be executed.

After that shared folders should be automatically mounted in your VM:

$ df -h Filesystem Size Used Avail Use% Mounted on vbkick 10G 1G 9G 10% /media/sf_vbkick To check whether virtualbox additions are installed you can run (if you are using template):

$ vbkick validate VM_NAME Virtualbox Guest Additions: OK ... By default this settings are used to configure shared folders (you can change this in the definition file): shared_folders=("vbkick:%PWD%:automount")

If you want mount shared folders as /vagrant something like this must be done inside the VM:

mount #check the share name -e.g. vbkick sudo umount vbkick sudo mkdir -p /vagrant sudo chown vagrant:vagrant /vagrant id vagrant #check uid and gid numbers sudo mount -t vboxsf -o rw,uid=500,gid=500 vbkick /vagrant/ You may want automate this process by creating postinstall/vagrant_sharefs.sh script or something similar and updating related entries in the definition file (or postinstall/adm_conxtext... if you are using that approach). The current templates don't do this because they just implement the minimum needed to export templates as a vagrant base boxes.

Advance example with shared folder is available here: https://github.com/wilas/vbkick-templates-forge/blob/master/Mer/definition-mersdk.cfg

To find more about shared folder options, please follow: https://www.virtualbox.org/manual/ch04.html#sharedfolders

NB: there is a bug in virtualbox v4.3.10 - https://www.virtualbox.org/ticket/12879 where the extra step is required to mount shared folder under custom location.

— Reply to this email directly or view it on GitHub.