title: What is the proper way to start a container after it has exited?
body: <p>I have a container called sqlcontainer1.
  The image is "microsoft/mssql-server-linux:2017-latest".
  I restored a .bak file to it and now I can use it for local development.
  And I can even see if from SSMS (SQL Server Management Studio).  Great!</p>
  
  <p>The problem is after I reboot it the container status says "Exited".</p>
  
  <p>The only way I can see to restart is to type:</p>
  
  <pre><code>docker start -ai sqlcontainer1
  </code></pre>
  
  <p>Then no command prompt is ever returned so I have to open another command prompt and retype:</p>
  
  <pre><code>docker ps -a
  </code></pre>
  
  <p>to see the status is now "UP 7 minutes".
  OK, I'm glad it's up and I can now connect back with SSMS and work from there (although I am wondering why it says 7 minutes. I've only had it up seconds).
  Good.</p>
  
  <p>But there has to be a better way.
  I just want two commands like this;</p>
  
  <pre><code>docker start containerName
  docker stop containerName
  </code></pre>
  
  <p>Is there anything like this?</p>
  
  <p>If I can get that far then I would like to look into a proper restart policy.</p>