title: What are the consequences of using "docker" and "docker-compose" commands interchangeably?
body: <p>I have several containers which are described in a <code>docker-compose-&lt;service&gt;.yaml</code> file each, and which I start with </p>
  
  <pre><code>docker-compose -f docker-compose-&lt;service&gt;.yaml up -d
  </code></pre>
  
  <p>I then see via <code>docker ps</code> the container running.</p>
  
  <p>I expected that I could stop that container via</p>
  
  <pre><code>docker-compose -f docker-compose-&lt;service&gt;.yaml down
  </code></pre>
  
  <p>The container is however not stopped. Neither it is when I use the comane above with <code>stop</code> instead of <code>down</code>.</p>
  
  <p>Doing a <code>docker kill &lt;service&gt;</code> stops the container.</p>
  
  <p><strong>My question: since all my services started with <code>docker-compose</code> are effectively one container for each <code>docker-compose-&lt;service&gt;.yaml</code> file, can I use the bare <code>docker</code> command to stop it?</strong></p>
  
  <p>Or more generally speaking: is <code>docker-compose</code> simply a helper for underlying <code>docker</code> commands which means that using <code>docker</code>  is always safe (from a "consistency in using different commands" perspective)?</p>