Now add the following to the file (no sudo needed): mkdir -p /mnt/src Create a file named bootlocal.sh at the following location: $ sudo touch /mnt/sda1/var/lib/boot2docker/bootlocal.sh What we need is a setup script that won’t be erased and will run on startup. The problem is everything gets erased whenever you restart your VM. You should now be able to view the contents of your directory within your Docker VM: $ ls /mnt/src I think the longer version is more clear and safe. You could just enter 1000 and 50 respectively and you’d be fine. Id -u docker and id -g docker will use the user id and group id respectively. The -p is just in case /mnt doesn’t already exist.Īdd your new mount: $ sudo mount -t vboxsf -o defaults,uid=`id -u docker`,gid=`id -g docker` src /mnt/src Just to review, so you don’t have to read the last post:Ĭreate a new folder for your mount: $ sudo mkdir -p /mnt/src In my last post I showed how to mount a VirtualBox shared folder but as soon as you restart ( that never happens on a Windows box) you’ve lost it and have to create the mount all over again. However, that’s the only default path you get when you create a boot2docker image for VirtualBox.
There’s no convenient ~/ command-line shortcut when typing the path on the command-line.msbuild blows up when your path is longer than 256 characters.The path used to start with C:\Documents and Settings\\.Historically there have been too many problems: While this technique works for both Windows and OSX, most Windows developers I know don’t keep their source code in the Users folder on the system drive. Menu Docker: Permanently Mount a VirtualBox Shared Folder
0 kommentar(er)
