What differences could be affecting a SOLR indexing when using Docker in EC2 rather than Docker-compose?
<p>I have a docker container with Solr in <strong>Amazon EC2</strong> using Amazon ECS <a href="https://github.com/datacite/search/blob/labs/Dockerfile" rel="nofollow noreferrer">(dockerfile)</a>. Takes a Database and save the index in an <strong>EFS volumen</strong>. As in my drawing.</p>

<p><a href="https://i.stack.imgur.com/gFsgv.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/gFsgv.png" alt="my setup"></a></p>

<p>However, the indexing is never complete and errors are never thrown out in the logs.</p>

<p>I have a similar setup on my local machine (without the EFS volume) but using <code>docker-compose</code> <a href="https://github.com/datacite/search/blob/labs/docker-compose.yml" rel="nofollow noreferrer">(.yml file)</a> and the indexing works pretty well. </p>

<p><em>I made an experiment</em>, I installed <code>docker-compose</code> in <strong>EC2</strong> and ran the same container. The results? The indexing works fine. It indexes the whole database. </p>

<p>I have found NO difference in:</p>

<ul>
<li>Env variables.</li>
<li>ran <code>Docker inspect</code> on either of the containers <a href="https://gist.github.com/kjgarza/8d8a80bab10e2c1c2e07f7e49deb6c16" rel="nofollow noreferrer">both files</a></li>
</ul>

<p>What could be causing the I have different results indexing the database when using <code>docker-compose</code> as oppose to using <code>ECS</code>??</p>