Node on Windows fails to bootstrap with Docker Desktop 3.1.0

[concordium-cl]

When running your node on Windows, it might fail to bootstrap. In that case, it will not get any peers and does not catch up to the chain or at least not to the full fin length. You can check both e.g. on the network dashboard. Furthermore, the log will show the following entries:

ERROR: Can't connect to the desired address
INFO: Attempting to bootstrap
INFO: No peers at all - retrying bootstrapping

The issue only occurs with the latest Docker Desktop version 3.1.0. The node works fine with when running with earlier Docker versions. However, since Docker from version 3.0.0 and upwards automatically updates to the latest version when restarting, we strongly recommend to install Docker Desktop 2.5.0.1, which comes with Docker Engine version 19.03.13.

• To check, which Docker Desktop version you have installed, right-click the Docker Desktop system tray icon (i.e. the whale carrying a stack of containers) and choose "About Docker Desktop". It should say 2.5.0.1 (or lower).
• To check, which Docker Engine version you have installed, run docker version in your terminal. It should say Version: 19.03.13 (or lower).

We suggest the following workaround:

• run concordium-node-stop
• run concordium-node-reset-data
• uninstall your current Docker software
• download Docker Desktop version 2.5.0.1 here
• install Docker Desktop version 2.5.0.1
• when the installation is completed, make sure Docker is running
• Whenever you are prompted that a new Docker Desktop is available, chose "Skip This Build" or "Remind me later". Never click "Install Update"!
• run concordium-node

Your node should now catch up to the full fin length and eventually get peers assigned.

Whenever you restart your node, remember to NOT UPDATE TO A NEWER VERSION.

[ZloyMyshok]

The question can be closed. Yes it really works! But I think that this is not correct. Node cannot support the latest Docker updates on Windows !!!

[concordium-cl]

Happy that it works for you. I don't see how a more imprecise statement makes the title more correct though.