moby: Container with docker overlay network doesn't work in windows container host
Output of docker version:
Client:
Version: 1.12.0-dev
API version: 1.24
Go version: go1.5.4
Git commit: 2f7c841
Built: Tue May 10 09:04:34 2016
OS/Arch: darwin/amd64
Server:
Version: swarm/1.2.2
API version: 1.22
Go version: go1.5.4
Git commit: 34e3da3
Built: Mon May 9 17:03:22 UTC 2016
OS/Arch: linux/amd64
Output of docker info:
Containers: 5
Running: 2
Paused: 0
Stopped: 3
Images: 5
Server Version: swarm/1.2.2
Role: primary
Strategy: spread
Filters: health, port, containerslots, dependency, affinity, constraint
Nodes: 2
vagrant: 192.168.33.12:2376
└ ID: UNDE:NGEB:25BY:ZPEL:FOSQ:FHRB:GQTC:XKIY:BPZR:N7JN:AGK2:FSN4
└ Status: Healthy
└ Containers: 1
└ Reserved CPUs: 0 / 2
└ Reserved Memory: 0 B / 4.053 GiB
└ Labels: executiondriver=, kernelversion=4.2.0-27-generic, operatingsystem=Ubuntu 14.04.4 LTS, storagedriver=aufs, type=linux
└ Error: (none)
└ UpdatedAt: 2016-05-17T13:47:41Z
└ ServerVersion: 1.12.0-dev
vagrant-windows: 192.168.33.11:2376
└ ID: UEWX:F6WP:BUUF:RHRU:COAR:LJVT:MDUQ:OMZY:RRFN:FPES:PHWX:ID5D
└ Status: Healthy
└ Containers: 4
└ Reserved CPUs: 0 / 2
└ Reserved Memory: 0 B / 4.2 GiB
└ Labels: executiondriver=, kernelversion=10.0 14300 (14300.1016.amd64fre.rs1_release_svc.160428-1819), operatingsystem=Windows Server 2016 Datacenter Technical Preview 5, storagedriver=windowsfilter, type=windows
└ Error: (none)
└ UpdatedAt: 2016-05-17T13:46:59Z
└ ServerVersion: 1.12.0-dev
Plugins:
Volume:
Network:
Kernel Version: 4.2.0-27-generic
Operating System: linux
Architecture: amd64
CPUs: 4
Total Memory: 8.252 GiB
Name: 30765c7e4fca
Docker Root Dir:
Debug Mode (client): false
Debug Mode (server): false
WARNING: No kernel memory limit support
Additional environment details (AWS, VirtualBox, physical, etc.):
Steps to reproduce the issue:
- docker network create -d overlay stage
- docker run -d --net stage stefanscherer/mongo-windows
Describe the results you received:
Fails with error message
docker: Error response from daemon: Error response from daemon: invalid CIDR address: GlobalDefault/10.0.0.0/24.
Describe the results you expected:
Should have run the container on the overlay network stage
Additional information you deem important (e.g. issue happens only occasionally):
The docker engines are configured properly to use consul key value store. The containers when run on the linux host attaches to the overlay network stage properly.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 40 (16 by maintainers)
Looks like overlay support for Windows is available now for Windows 10 insider https://blogs.technet.microsoft.com/virtualization/2017/02/09/overlay-network-driver-with-support-for-docker-swarm-mode-now-available-to-windows-insiders-on-windows-10/
@friism, thanks for sending this detailed workshop. On overlay network without swarm mode, is this functionally going to be removed from Docker any time soon or just deprecated? Our setup is currently based on Consul + Docker + Nomad using overlay network without swarm mode and it will be helpful if you can expand on Docker plans for multi-host networking.
To summarize, Docker 17.04+ paired with either Windows 10 Creators Update or WS2016 with KB4015217 how supports overlay networking.
As @StefanScherer points out, ingress load balancing does not yet work on Windows.
@thaJeztah this issue can probably be closed now.
The KB4015217 brings overlay to Windows 2016, not the routing mesh.
This wasn’t super discoverable (didn’t see updates on the various issues related to this), but there is a new KB for Windows Server 2016 to add overlay Network support:
https://support.microsoft.com/en-us/help/4015217/windows-10-update-kb4015217
Overlay network(that’s available in Linux) is not supported in Windows for now. We do have L2Bridge and L2Tunnel networking modes which are windows specific networking modes designed for SDN for Microsoft Azure stack and Azure.