title: Problem with shared volume write permissions using minikube as a docker desktop replacement
body: <p>So the problem is quite simple,</p>
  <p>I want to use minikube with docker for the local development alone, without docker desktop app or kubernetes itself.</p>
  <p>Everything works smoothly until I wanted to use a shared volume to persist changes on my local disk after I run <code>minikube delete</code>. My setup is hypervisor + minikube + docker on MacOS system.</p>
  <p>To be specific, here is the commands I run:</p>
  <p><code>minikube start --no-kubernetes</code></p>
  <p><code>minikube mount /private/var/services/:/private/var/services/</code></p>
  <p><code>docker run --name redis -p 6379:6379 -v /private/var/services/redis:/data redis:5  </code></p>
  <p>and the result of the last command is:</p>
  <p><code>docker: Error response from daemon: error while creating mount source path '/private/var/services/redis': mkdir /private/var/services/redis: errno 526.</code></p>
  <p>I tried to do the same with mongodb and result is always the same: lack of permissions to write to the shared volume.</p>
  <p>If I change volume on docker to be somewhere else: eg.: <code>docker run --name redis -p 6379:6379 -v /tmp/redis:/data redis:5</code> – it works just fine</p>
  <p>I already spent some time to debug it, like mounting minikube volume with another gid/uid, but no luck.</p>
  <p>Temp solution, that I came up with is mounting to <code>/data/*</code>, but this approach works until first minikube delete command.</p>
  <p>Please share what's your experience using minikube as a docker runner</p>