title: Running docker-Desktop on Windows 10 cannot restart containers after system restart
body: <p>I am running Docker-Dektop Version 2.1.0.0 (36874) on a Windows 10 environment.
  I am using two separate container compositions, one of these binding to port 8081 on my machine, and the other binding to 9990 and 8787.</p>
  
  <p>After a system restart, I am unable to start these container compositions again, because the ports are already bound.</p>
  
  <p>So far, I have tried multiple approaches to solve this:</p>
  
  <ul>
  <li>manually stop all containers prior to system shutdown</li>
  <li>manually stop and remove all containers prior to system shutdown</li>
  <li>the above, plus explicitly stopping the docker application prior to system shutdown</li>
  <li>removing all containers after system startup and prior to restart</li>
  <li>pruning the networks after container removal</li>
  <li>restart docker app prior to restarting containers (this worked up until the last update)</li>
  </ul>
  
  <p>I did fiddle around with the compose files and the configuration, but taht would be too much detail to go into right now; all of these did not help.</p>
  
  <p>What I recently found was, directly after a system startup and prior to starting any container, that the process <code>com.docker.backend</code> was already listening to the bound ports. This is confusing as the containers were shut down prior to system shutdown and are not run with a restart-command.</p>
  
  <p>So I explicitly quit the docker desktop app, and the process still remaind, and it still bound the ports.</p>
  
  <p>After manually killing the process as administrator from the power shell, and restarting the docker desktop application, my containers were able to start again.</p>
  
  <p>Has anyone else had this problem? Does anyone know a "fix" for this at all?</p>
  
  <p>And, of course, is this even the right page to ask? As this is not strictly programming, I am unsure.</p>