<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>

<p>You can convert <em>docker-compose.yaml</em> files with a tool called <a href="https://kompose.io/" rel="nofollow noreferrer"><code>kompose</code></a>.<br />
It's as easy as running</p>
<pre class="lang-text prettyprint-override"><code>kompose convert
</code></pre>
<p>in a directory containing <em>docker-ccompose.yaml</em> file.<br />
This will create a bunch of files which you can deploy with <code>kubectl apply -f .</code> (or <code>kompose up</code>). You can read more <a href="https://kubernetes.io/docs/tasks/configure-pod-container/translate-compose-kubernetes/" rel="nofollow noreferrer">here</a>.</p>
<p><strong>However</strong>, even though <code>kompose</code> will generate PersistentVolueClaim manifests, no <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/" rel="nofollow noreferrer">PersistentVolumes</a> will be created. You have to make those yourself (cluster may try to create PVs by itself, but it's strongly based on PVCs generated by <code>kompose</code>, I would not rely on that).</p>
<hr />
<p>Docker compose is mainly used for devlopment, testing and single host deployments <sup>[<a href="https://docs.docker.com/compose/#common-use-cases" rel="nofollow noreferrer">reference</a>]</sup>, which is not exactly what Kubernetes was created for (latter being cloud oriented).</p>
