-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Description
File: content/manuals/desktop/features/networking/_index.md
Issue
The documentation makes a platform-specific statement appear universal:
All outbound container network traffic originates from the
com.docker.backendprocess. Firewalls, VPNs, and security tools, like Crowdstrike, see traffic coming from this process — not from a VM or unknown source so firewall and endpoint security software can apply rules directly tocom.docker.backend.
This statement uses com.docker.backend as if it applies to all platforms, but according to the backend components table in the same file:
- Windows uses
com.docker.backend.exe(notcom.docker.backend) - Mac uses
com.docker.backend - Linux uses
qemu(notcom.docker.backend)
Users on Windows or Linux following this guidance would look for the wrong process name when configuring firewalls or endpoint security tools.
Suggested fix
Rewrite to acknowledge platform differences:
All outbound container network traffic originates from the Docker Desktop backend process (`com.docker.backend.exe` on Windows, `com.docker.backend` on Mac, or `qemu` on Linux). Firewalls, VPNs, and security tools, like Crowdstrike, see traffic coming from this process — not from a VM or unknown source, so firewall and endpoint security software can apply rules directly to the appropriate process for your platform.Found by nightly documentation freshness scanner