Symbolic links don't work in Mounted Host Folders

[tslater]

Minikube version: v0.12.2

Environment:

• OS : MacOS v10.12.1
• VM Driver: xhyve
• Docker version (e.g. docker -v): Docker version 1.12.2
• Install tools: brew

What happened:
I received an error "ln: symlinktestfilelinked.txt: Operation not permitted"

What you expected to happen:
Create a successful symbolic link

How to reproduce it (as minimally and precisely as possible):

minikube ssh
cd /Users/your-user-dir
touch symlinktestfilesource.txt
ln -s symlinktestfilesource.txt symlinktestfilelinked.txt 

Anything else do we need to know:
This is important to me because I try and do things like npm install inside the container (for local development), and I'll get errors about it not being able to make symbolic links.

[iameli]

Anyone have any ideas for this? This blocks the xhyve driver for our use case, which is a shame 'cause it's otherwise so much faster. I'd love to spend some time digging into it, but I have no idea where to start.

[SpencerMalone]

Any updates? I did note that this is the case for the default more custom configured /Users folder, as well as folders mounted with minikube mount

[SpencerMalone]

Interestingly, with the virtualbox driver, the following behavour is exhibited:

• When looking in the default /Users folder on a mac, symbolic links work

• If you mount a directory using minikube mount, the symbolic links will NOT work

ex:

$ cd /mnt/web/_domains/login/
$ ls -l
total 7
<redacted>
-rwxr-xr-x 1 4294967294 4294967294  13 Aug  1  2016 _cache
<redacted>
$ cd  Users/<redacted>/web/_domains/login/
$ ls -l
total 48
lrwxr-xr-x 1 docker docker  13 Aug  1  2016 _cache -> ../../_cache/

EDIT: Guess that makes sense, looking at it. One is a shared folder on the VM, the other is a mount using 9p like with xhyve. Is this a limitation with 9p?

[gh-aw]

I too am running in to this issue in the same environment as above. Any word on this?

[scheler]

+1

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[iameli]

FWIW this issue moved our team from minikube to Kubernetes for Docker for Mac, which is working fine

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[jpswade]

This is still an issue with minikube.

oot@deca1a6f4779:/usr/src/test# touch test
root@deca1a6f4779:/usr/src/test# ln -s test test1
ln: failed to create symbolic link 'test1': Operation not permitted

[jpswade]

@iameli What was the fix? Could it be brought into minikube? Is minikube abandoned in favour of Docker for Mac?

[marxangels]

/reopen

[k8s-ci-robot]

@toruksmakto: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.