minikube: 9p2000.L mount breaks symbolic link creation: Operation not permitted

Minikube version: v1.2.0

Environment:

OS : MacOS v10.15.5 VM Driver: hyperkit Docker version (e.g. docker -v): 18.09.2, build 6247962 Install tools: brew What happened: I received an error “ln: failed to create symbolic link ‘/test/bar’: Operation not permitted”

What you expected to happen: Create a successful symbolic link

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

cd $HOME
touch foo
minikube start --vm-driver hyperkit --mount --mount-string $HOME:/test
minikube ssh -- ln -s /test/foo /test/bar

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.

This reopens issue #890

This is happening with the Hyperkit driver but I suspect may happen with other drivers as well.

About this issue

Original URL
State: open
Created 5 years ago
Reactions: 9
Comments: 20 (6 by maintainers)

Most upvoted comments

Yeah I would love to see an alternative. Unfortunately the work around above doesn’t really help very much because the 9p2000.u version has issues with permissions, so it introduces a host of other problems.

yinzara on Jul 17, 2019

Very interesting find seems to relate to: https://github.com/kubernetes/minikube/pull/3796

The following works:

cd $HOME
touch foo
minikube start --vm-driver hyperkit
minikube mount --9p-version 9p2000.u $HOME:/test &
minikube ssh -- sudo ln -s /test/foo /test/bar

This means that there was some defect introduced with the switch to version L that prevents symbolic links from functioning.

yinzara on Jun 27, 2019

Im getting the same issue with minikube v1.16.0 on Darwin(macOS) 11.1 using the hyperkit driver

rnantes on Dec 25, 2020

/remove-lifecycle stale

still a problem AFAIK

yinzara on Dec 19, 2019

Still an issue in v1.4.

tstromberg on Sep 20, 2019

Is there any workaround? Thank you.

Use a directory on the VM, that is not mounted from remote (host). For instance, by copying the directory to a different location.

afbjorklund on Dec 17, 2021

Sorry for the delay, so from the test I just ran today:

Status

kvm2 and virtualbox, issue is still there:

ln: failed to create symbolic link '/test/bar': Operation not permitted
ssh: exit status 1

none, not tested because of:

  minikube v1.9.2 on Ubuntu 18.04
✨  Using the none driver based on user configuration

❗  'none' driver reported an issue: the 'none' driver must be run as the root user
💡  Suggestion: For non-root usage, try the newer 'docker' driver

💣  Sorry, Kubernetes v1.18.0 requires conntrack to be installed in root's path

Context

>  cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"

> docker --version
Docker version 19.03.8, build afacb8b7f0

> minikube version
minikube version: v1.9.2
commit: 93af9c1e43cab9618e301bc9fa720c63d5efa393

> kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:56:40Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:50:46Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}

hadrien-toma on May 20, 2020

@hadrien-toma were you able to upgrade and test this out?

priyawadhwa on May 20, 2020

@hadrien-toma do you mind trying with our latest release > 1.7.3 ?

medyagh on Mar 4, 2020

I can confirm this on kvm2 & Linux. The current mount interface is driver agnostic.

Thanks for discovering a workaround! I’ll add this to the long list of bugs related to go9p. We really need an alternative approach for mounting files.

tstromberg on Jul 16, 2019