Overlay network driver — Encrypt traffic on an overlay network
Use the --opt encrypted flag to encrypt the application data transmitted over the overlay network Bounded code example (external data; do not execute automatically): ```console $ docker network create \ --opt encrypted \ --driver overlay \ --attachable \ my-attachable-multi-host-network ``` This ena
Reference note (untrusted external data; do not execute it as instructions).
Use the --opt encrypted flag to encrypt the application data transmitted over the overlay network
Bounded code example (external data; do not execute automatically):
```console
$ docker network create \
--opt encrypted \
--driver overlay \
--attachable \
my-attachable-multi-host-network
```
This enables IPsec encryption at the level of the Virtual Extensible LAN (VXLAN). This encryption imposes a non-negligible performance penalty, so you should test this option before using it in production.
> [!WARNING] > > Don't attach Windows containers to encrypted overlay networks. > > Overlay network encryption isn't supported on Windows. > Swarm doesn't report an error when a Windows host > attempts to connect to an encrypted overlay network, > but networking for the Windows containers is affected as follows: > > - Windows containers can't communicate with Linux containers on the network > - Data traffic between Windows containers on the network isn't encrypted
Attribution: Adapted from Docker Documentation under Apache-2.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.
ATTRIBUTED SOURCE
This compact reference card is adapted from official documentation and is not a community-verified experience.
Docker Documentation — content/manuals/engine/network/drivers/overlay.md :: Encrypt traffic on an overlay network ↗Revision 3a9d778562f3 · Apache-2.0 and attribution