-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
canot ready directory 'xyz/': Unknown error 526 #8732
Comments
Hey @artemkoslenkov thanks for opening this issue. What version of minikube are you running? |
Hi there, minikube version: v1.11.0 |
just upgraded to v1.12.0
basicaly any folder related operations (r+w+x) will throw error 526 |
@artemkoslenkov what driver are you using ? do you have same issue with any other driver that minikube supports ? |
/triage needs-information |
Hi, I'm using kvm2 driver on ubuntu, haven't checked with other drivers. May it be related to what's mentioned here https://minikube.sigs.k8s.io/docs/handbook/mount/ regarding folders > 600 files issue? In node_modules this may definitely be the case. How to work around this case? Many thanks, |
You can use driver mounts as an alternative to 9p mounting, although that isn't supported in kvm2. It would require use of another driver (virtualbox perhaps?). |
thanks for your reply, however, this sounds more like jigery pokery © solution, that's why i consider changing the way I handle dependencies for Node and instead of mounting node_modules simply run npm install inside the container or minikube node, this is however, impo, not consitent with |
I faced this same issue a few days ago, I could solve it tho by booting my cluster up and mounting the directory running this:
For this you would have to have docker daemon up and running. |
Hello everybody, I'm running into this on
ls -la /node_modules
for the mounted folder inside the minikube cluster,
issue1562
PR1705
but still no luck.
the folder size is 187 mb only, how big should
--msize
be?Any help would be much appreciated.
The text was updated successfully, but these errors were encountered: