<p>I was given a docker compose file for superset which included volumes mounted from the repo itself.
<a href="https://github.com/apache/superset/blob/master/docker-compose-non-dev.yml" rel="nofollow noreferrer">docker-compose-non-dev.yml</a></p>
<p>I have to deploy this as containers in a pod in an EKS cluster. I can't figure out how the volumes should be done because the files are mounted locally from the repo when we run:</p>
<pre><code>docker-compose up
</code></pre>
<p>[ EDIT ]
I just built the container with the files I needed inside it.</p>

Harikrishnan A
<p>Docker compose is a tool geared towards local deployments (as you may know) and so it optimizes its workflows with that assumption. One way to work this around is by wrapping the docker image(s) that compose <code>up</code> with the additional files you have on your local environment. For example a wrapper <code>dockerfile</code> would be something like</p>
<pre><code>FROM &lt;original image&gt;
ADD &lt;local files to new image&gt;
</code></pre>
<p>The resulting image is what you would run in the cloud on EKS.</p>
<p>Of course there are many other ways to work it around such as using Kubernetes volumes and (pre-)populating them with the local files, or bake the local files in the original image from the get go, etc.</p>
<p>All in all the traditional compose model of thinking (with local file mappings) isn't very &quot;cloud deployments friendly&quot;.</p>
