shaneknapp edited a comment on issue #23514: [SPARK-24902][K8s] Add PV 
integration tests
URL: https://github.com/apache/spark/pull/23514#issuecomment-461636214
 
 
   > anyways, this is all moot as it just won't work:
   > 
[kubernetes/minikube#1822](https://github.com/kubernetes/minikube/issues/1822)
   > 
   > TL;DR: you can only mount folders owned by the user running the cluster. 
/tmp is owned by root. no bueno.
   > 
   also confirmed by manually adding a `<filesystem>` share for `/tmp` in the 
virsh config of the minikube cluster and the cluster failing to come up:
   
   ```
   $ virsh start minikube
   error: Failed to start domain minikube
   error: internal error: process exited while connecting to monitor: 
2019-02-07T23:33:33.707441Z qemu-system-x86_64: -device 
virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=testlabel,bus=pci.0,addr=0x8: 
Virtio-9p Failed to initialize fs-driver with id:fsdev-fs0 and export path:/tmp
   ```
   
   same exact error when using minikube:
   ```
   $ minikube --vm-driver=kvm2 start --memory 6000 --cpus 8 
--mount-string="/tmp:/tmp2" --mount
   Starting local Kubernetes v1.10.0 cluster...
   Starting VM...
   E0207 15:33:01.434290   18298 start.go:159] Error starting host: Error 
starting stopped host: Error creating VM: virError(Code=1, Domain=10, 
Message='internal error: process exited while connecting to monitor: 
2019-02-07T23:33:01.274917Z qemu-system-x86_64: -device 
virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=testlabel,bus=pci.0,addr=0x8: 
Virtio-9p Failed to initialize fs-driver with id:fsdev-fs0 and export 
path:/tmp').
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to