Failure to setup ICMPv6 forwarding prevents Docker Desktop from starting ("context deadline exceeded")

[andrea-reale]

Description

This bug was originally reported in #14294 (comment).

A failure to setup ICMPv6 forwarding in Docker Desktop, which causes the host-vm networking stack (gvisor) to fail. The visible symptom is Docker Desktop failing to startup. The error message appears to be not consistent (possibly depending on the concurrent startup sequence), but the most common reported error occurs after a deadline waiting for dockerd to be up and running:

• running engines: engines watcher: running engine: waiting for the Docker API: context deadline exceeded

The issues was likely introduced in Docker Desktop 4.31, where ICMPv6 forwarding was added.

Reproduce

It's still unclear what the conditions for triggering the ICMPv6 setup failures are. One customer reports not having any specific IPv6 restrictions, except a Glasswire firewall (original comment).

Expected behavior

No response

docker version

{
  "id": "33CD9446-CCD2-4B86-851B-5743B3A48BE2",
  "date": "2024-09-02 18:41:54.9643034 +0000 UTC",
  "os": "Windows 11 Enterprise 10.0.22631",
  "os_label": "win/22631",
  "app_version": "4.34.0",
  "app_channel": "main",
  "engine_version": "27.2.0",
  "compose_version": "v2.29.2-desktop.2",
  "kubernetes_version": "v1.30.2",
  "credhelper_version": "v0.8.2"
}

docker info

NA

Diagnostics ID

33CD9446-CCD2-4B86-851B-5743B3A48BE2/20240902184148

Additional Info

No response