Thanks for answering, do I understand correctly that you develop directly on CoreOS with Emacs? If so I think your workflow might be more of an outlier as I reckon most people tend to work on OSX (possibly even running some IDE of some sorts).<p>I think a lot of confusion comes from unclear definitions so I try my best here, it would be great if you could chip in once again...<p># Premise<p>1. our base operating system is Mac OSX which we will simply call <i>osx</i><p>2. on top of <i>osx</i> we run a <i>hypervisor</i> (e.g. xhyve, vmware, virtualbox)<p>3. on top of our <i>hypervisor</i> we are running a virtual machine with CoreOS as our <i>docker_engine</i> (with the help of or without vagrant)<p>4. on top of our <i>docker_engine</i> we run an arbitrary set of <i>docker_container</i> instances most of which are comprised of a &quot;bespoke&quot; <i>docker_image</i> of our own; a certain &quot;microservice&quot; in development<p># Questions<p>How do we:<p>a) map a (&quot;microservice&quot;) project&#x27;s source code directory located on our <i>osx</i> file system onto the currently instantiated development <i>docker_image</i> for our current project&#x27;s development <i>docker_container</i><p><i>osx</i> =&gt; <i>hypervisor</i> =&gt; <i>docker_engine</i> =&gt; <i>docker_container</i><p>b) and pass any file changes from <i>osx</i> down to the <i>docker_container</i> level as well (i.e. inotify, lsyncd, etc)<p>BTW, if we&#x27;d wanted to make this an even more helpful effort why not make this a proper gist?<p><a href="https:&#x2F;&#x2F;gist.github.com&#x2F;musha68k&#x2F;399c66374ca54c665fd5" rel="nofollow">https:&#x2F;&#x2F;gist.github.com&#x2F;musha68k&#x2F;399c66374ca54c665fd5</a>