<p>Kubernetes features quite a few types of volumes, <a href="https://kubernetes.io/docs/concepts/storage/volumes/#types-of-volumes" rel="noreferrer">including <code>emptyDir</code></a>:</p>
<blockquote>
<p>An <code>emptyDir</code> volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. As the name says, it is initially empty. Containers in the pod can all read and write the same files in the <code>emptyDir</code> volume, though that volume can be mounted at the same or different paths in each container. When a Pod is removed from a node for any reason, the data in the <code>emptyDir</code> is deleted forever.</p>
<p>...</p>
<p><strong>By default, emptyDir volumes are stored on whatever medium is backing the node.</strong></p>
</blockquote>
<p>Is the <code>emtpyDir</code> actually mounted on the node, and accessible to a container outside the pod, or to the node FS itself?</p>

<p>Yes it is also accessible on the node. It is bind mounted into the container (sort of). The source directories are under <strong><code>/var/lib/kubelet/pods/PODUID/volumes/kubernetes.io~empty-dir/VOLUMENAME</code></strong></p>

<p>You can find the location on the host like this:</p>

<pre><code>sudo ls -l /var/lib/kubelet/pods/`kubectl get pod -n mynamespace mypod -o 'jsonpath={.metadata.uid}'`/volumes/kubernetes.io~empty-dir
</code></pre>
