shaneknapp edited a comment on issue #23514: [SPARK-24902][K8s] Add PV integration tests URL: https://github.com/apache/spark/pull/23514#issuecomment-461577129 > @shaneknapp I dont want to test hostpath as it is not something people likely want to use as a feature (not secure and not pretty useful). > PV test is important. > Actually you mount the host /tmp to vm's /tmp not the pod. > So the mounting should be: > /tmp (host) -> some/folder (vm) -> /tmp(pod) (not the other way around, order matters) > yeah, i got it. i wasn't describing what i was doing that accurately. anyways, this is all moot as it just won't work: 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. i used the process on this page to perform my testing: https://github.com/kubernetes/minikube/blob/master/docs/host_folder_mount.md we're trying to mount a folder (/tmp) from the host machine to the VM as /tmp. this mount doesn't actually fail. what fails is when you try to spin up a container in a new pod to mount that has the final mount point, and we get a collision between that final container's /tmp not having permission to write to the host system /tmp. i also tried a symlink in the jenkins homedir to /tmp, which also failed. mounting and modifying directories owned by jenkins did work as expected. so: the reason why this works for you is that you aren't using a VM driver, so the processes need root-level access to do things like mount and modify /tmp. `sudo minkube etc etc`... make sense? there's no way i'm giving the jenkins user on the workers root-level access to things. nor does `chowning` /tmp to be owned by jenkins seem reasonable for this one test. :\ thoughts? i could be wrong, but i really don > Why remote file test is broken? orthogonal, and almost definitely caused by the above issues.
---------------------------------------------------------------- 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]
