starting docker containers does not work on first try

[wright-stuff]

Containers were rebuilt on fs computer today (we were using an old version of bluesky-in-a-box), and upon bluesky-in-a-box package startup some containers are closed immediately:

• hw-proxy
• re-manager
• slack
• wt5 hw-proxy and re-manager give me HTTP error messages e.g.

  (HTTP code 500) server error - Ports are not available: exposing port TCP 0.0.0.0:60615 -> 0.0.0.0:0: listen tcp 0.0.0.0:60615: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

(This is for re-manager; for hw-proxy the port is 60620) Pressing the run command after the error shuts it down reproduces this issue; pressing the restart button, however clears the errors.

After both hw-proxy and re-manager are restarted, slack and wt5 can simply be started.

Not sure why the ports are initially forbidden in such a way that restarting gets rid of the issue...

[wright-stuff]

may be due to a new port exclusion?

netsh interface ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges

Start Port    End Port
----------    --------
      8000        8000
      8002        8002
      8004        8004
      8006        8006
     50000       50059     *
     60537       60636
     60637       60736
     60737       60836
     60837       60936
     60937       61036
     61037       61136
     61137       61236
     61237       61336
     62495       62594
     62595       62694
     62695       62794
     62795       62894
     62895       62994
     62995       63094
     63095       63194
     64244       64343

[wright-stuff]

trying fix https://github.com/docker/for-win/issues/3171

[wright-stuff]

restarting the computer did change the excluded ports and docker started up without incident. I will use the fix of keeping our ports out of the dynamic range; I am just waiting to consider what range is sufficient to avoid issues