Creating Symbolic Link Protocol Error
Contents |
Opened 13 months ago Last modified 12 months ago Symbolic links with `..` result in `protocol error` on vboxsf + 5.0.4 Reported by: scoates Owned by: Priority: major Component: shared folders Version: VirtualBox 5.0.4 Keywords: Cc: sean@… Guest type: Linux Host type: Mac OS X failed to create symbolic link protocol error vagrant Description When creating a symlink that contains .., we're seeing "protocol error" messages. For error creating symbolic link file exists this example /vagrant is none on /vagrant type vboxsf (rw,nodev,relatime). cd /vagrant ; mkdir test ; cd test ; ln -s ../Vagrantfile creating symbolic link linux . ln: failed to create symbolic link `./Vagrantfile': Protocol error This also happens when linking .. and not into the root. It does not happen when linking .. outside of the vboxsf system. This happens
Creating Symbolic Link Unix
for us on 5.0.4r102546 but not on 5.0.0r101573. It may be related to the following: https://www.virtualbox.org/ticket/14463 https://www.virtualbox.org/ticket/14153 Note: if the symlink is made on the host FS (and not created on the VM), it seems to behave normally/correctly. Host for our tests is Mac OS X 10.10, guest is Debian Jessie. Change History comment:1 Changed 13 months ago by scoates Also worth noting: I can successfully create symlinks on the creating symbolic link ubuntu vboxsf filesystem that do not contain .. comment:2 Changed 13 months ago by cama900 Just wanted to add my voice to this. Took me hours to figure out the problem because it occurred by trying to run npm install, not just making symlinks comment:3 Changed 13 months ago by scoates FWIW, mine happened when doing an automated-at-provisioning git checkout (which happened to contain ../ symlinks). comment:4 follow-up: ↓ 5 Changed 13 months ago by sunlover Fixed in https://www.virtualbox.org/download/testcase/VirtualBox-5.0.5-102721-OSX.dmg Please test whether this build it works for you. Thanks. comment:5 in reply to: ↑ 4 Changed 13 months ago by frastel Replying to sunlover: Fixed in https://www.virtualbox.org/download/testcase/VirtualBox-5.0.5-102721-OSX.dmg Please test whether this build it works for you. Thanks. I had the same problem. My setup: VirtualBox Version 5.0.4 OS X 10.10.5 docker-machine version 0.4.1 Vagrant 1.7.4 Symlinks are working again with your posted 5.0.5 testversion. Looks good to me! comment:6 Changed 13 months ago by scoates Confirmed. Works for me on 5.0.5r102721. Thanks! Looking forward to 5.0.5-actual comment:7 Changed 13 months ago by aleksandrvin Works for me. Macbook Pro Mid 14, 10.10.5 comment:8 Changed 12 months ago by justink Any timeline when 5.0.5 will be shipped? This bug is affecting us, we can't run npm install (because it uses relative symbolic links). comment:9 Chang
[ DST ] Get VirtualBox Forum powered by phpBB © phpBB Group By any use of this Website, you agree to be bound by these Policies and Terms of Use Sponsored by
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow http://unix.stackexchange.com/questions/197642/getting-protocol-error-when-trying-to-create-a-symlink-in-docker the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and symbolic link rise to the top Getting “Protocol Error” when trying to create a symlink in Docker up vote 3 down vote favorite I'm trying to setup a symlink, using the command ln -s /var/www/data/cache/widget/overlay/ /var/www/public_html/images/overlay but it outputs ln: failed to create symbolic link '/var/www/public_html/images/overlay': Protocol error The host OS is Windows 8, and the Docker image is Ubuntu. I believe the issue could be something to do with permissions, as when the Docker image creating symbolic link is started, /var/www/public_html is mapped to a folder inside Windows 8, /C/Users/Username/Documents/development/public_html. However, I can create folders, and files via command line inside the public_html folder, which kind of goes against it being permissions. I also can't find anyway to start Docker as admin to see if that helps, as it's just a .sh script that runs. Has anybody else had the "Protocol error" when creating symlinks? Or any idea how I could get more information about what causes this issue? EDIT: Also, if I try to save an image via PHP to the public_html folder or copy a file there (again, via PHP), that gives the same "Protocol error" message. ubuntu windows symlink virtual-machine docker share|improve this question edited Apr 22 '15 at 2:51 Scott 3,75621328 asked Apr 21 '15 at 14:44 Tom Hart 19019 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted So /var/www/public_html is actually as Windows folder, but /var/www/data is not? You're trying to create a symbolic link from a Windows directory into a Ubuntu directory in a virtual machine. There's no way that Windows can support an object like that. share|improve this answer answered Apr 22 '15 at 2:58 Scott 3,75621328 Yeah that's right. It's mounted as a data volume using this, ` -v /c/Users/TomHarto/Documents/development/public_html:/var/www/public_html