Unable to npm install certain modules in mounted directories

[cmaher]

BUG REPORT

Minikube version:
minikube version: v0.19.1

Environment:

• OS: macOS X 10
• VM Driver: VirtualBox
• ISO version: v0.18.0

What happened:
npm install grpc fails in directories mounted from the host and succeeds in standard directories

What you expected to happen:
npm install grpc should succeed in mounted directories

How to reproduce it (as minimally and precisely as possible):
Create the following pod:

---
apiVersion: v1
kind: Pod
metadata:
  name: node-runner
spec:
  containers:
  - image: node:6
    name: node-runner
    command: ["bash"]
    args:
    - -c
    - >
      trap : TERM INT;
      sleep 100000d & wait
    volumeMounts:
    - mountPath: /mounted
      name: codebase
  volumes:
  - name: codebase
    hostPath:
      path: /some/path/on/host/system

shell into the pod and run

$ cd /mounted
$ npm install grpc@1.3.8
# this fails with
# ENOENT: no such file or directory, chmod '/mounted/node_modules/grpc/node_modules/node-pre-gyp/node_modules/mkdirp/bin/cmd.js'
$ cd /root
$ npm install grpc@1.3.8 
# this succeeds

[r2d4]

Can you try running mount with the --v 10 flag and provide that output?

[cmaher]

I was originally using the /Users default mount. When manually mounting, I get a different error

glob error { Error: Unknown system error -526: Unknown system error -526, scandir '/mounted/node_modules/.staging/lodash-dae25555'
    at Error (native)
  errno: -526,
  code: 'Unknown system error -526',
  syscall: 'scandir',
  path: '/mounted/node_modules/.staging/lodash-dae25555' }

The log for this is in this 28MB gist:https://gist.github.com/anonymous/9327800bb81c0b9aedbb7b3586b92a56

Is there a way to log the default mount?

[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

[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