Node not starting after docker update

Node Operators troubleshooting
,
110
111

looks like working :slight_smile: It is new day, so graph gone to 0

112

had about 4-5 hours of downtime untill it was fixed

113

Yes, I tried everything with the last Docker version (stop/start service, authorize all the dockers ressources in the Windows firewall, disable firewall/antivirus & install back/reboot, factory reset, uninstall/reboot/install), but it was the same error message.

I can confirm it was a problem with the last Docker Desktop 2.2.0.0, and Iā€™m pretty sure Iā€™m not alone (because I didnā€™t changed anything between these updates, but this one is major, from 2.1 to 2.2) and it will be a hotfix eventually. They changed something in the network, it shows a different subnet in their new GUI/settings, that was weird. But Iā€™m back in 2.1.0.5.

I would like move to the GUI, but Iā€™m not sure Iā€™ll be able to run the two nodes like Docker listening on the two separate subnets. Does the GUI software is able to listen on all the network interfaces of Windows 10 or only the one I use to connect to Internet? And can I fall back my GUI node to docker if it fails ?

So my advice for Docker Desktop users: from my own experience, I advice you to do not upgrade at this time (skip this build button). In any case youā€™re screwed like me after this upgrade, uninstall/install back the older version you can grab on this page, resolved the issue : https://docs.docker.com/docker-for-windows/release-notes/ . Do not forget to map again the drives, ressources in the Docker settings after installation.

114

Yeah, I was also maybe 4 hours + 1 hour of downtime this month for one node, that hurts a bitā€¦ But it shoud be okay I think if youā€™re online now for the month and the next onesā€¦

Also, we learn from that kind of ā€œcrisisā€ of storage node each time a new accident happens. hehe.

Enjoy your node and have a nice day. Thanks for your support deathless, Vladim & Alexey.

115

For right now you donā€™t have to worry about this yet, disqualification for downtime is disabled.

1 Like
116

The reason is problably here:

DockerNAT has been removed from Docker Desktop 2.2.0.0 as using an IP address to communicate from the host to a container is not a supported feature. To communicate from a container to the host, you must use the special DNS name host.docker.internal . We also recommend using ports to communicate from the host to a container. For more information, see Networking.

However, if your current setup relies on IP addresses for communication, you can use a temporary workaround to reinstate DockerNAT. To do this, open C:\Program Files\Docker\Docker\resources\MobyLinux.ps1 and add $SwitchName = "DockerNAT" between line 175 and 176. Note that the temporary workaround to reinstate DockerNAT may be removed from future releases.

It is using DockerNAT on the previous version, but Iā€™m not sure to understand how use that host.docker.internal.

Does somebody installed the node on the lastest version of Docker?