title: Reuse containers with `docker-compose`
body: <p>I've an app running on multiple Docker containers defined by <code>docker-compose</code>. Everything works fine from my user and the <code>docker-compose ps</code> output looks like:</p>
  
  <pre><code>       Name                Command           State     Ports
  ------------------------------------------------------------
  myuser_app_1    /config/bootstrap.sh   Exit 137
  myuser_data_1   sh                     Exit 0
  myuser_db_1     /run.sh                Exit 143
  </code></pre>
  
  <p>Now I'm trying to run <code>docker-compose up</code> with <code>supervisord</code> (see relevant part of <code>supervisord.conf</code> below) and the issue is that the containers are now named <code>myapp_app_1</code>, <code>myapp_data_1</code> and <code>myapp_db_1</code>, that is they're created from scratch and all customizations on the former containers is lost.</p>
  
  <p>I tried renaming the containers, but it gives an error saying that there's already a container with that name.</p>
  
  <p><strong>Q:</strong> Is there some way to force <code>docker-compose</code> reuse existing containers instead of creating new ones based in their respective images?</p>
  
  <blockquote>
    <p>supervisord.conf</p>
  
  <pre><code>...
  [program:myapp]
  command=/usr/local/bin/docker-compose
      -f /usr/local/app/docker-compose.yml up
  redirect_stderr=true
  stdout_logfile=/var/log/myapp_container.log
  stopasgroup=true
  user=myuser
  </code></pre>
  </blockquote>