The 'nat' network is the default network for containers running on Windows. An external vSwitch is one that is directly connected to a network adapter on the container host.An internal vSwitch is one that isn't directly connected to a network adapter on the container host.If there are any pre-existing external vSwitches on the host which were created through PowerShell or Hyper-V Manager, they will also be available to Docker using the transparent network driver and can be seen when you run the docker network ls command. The first time the Docker engine runs, it will create a default NAT network, 'nat', which uses an internal vSwitch and a Windows component named WinNAT. Depending on your physical network infrastructure and single- vs multi-host networking requirements, you should choose the network driver which best suits your needs. Windows supports five different networking drivers or modes which can be created through Docker: nat, overlay, transparent, l2bridge, and l2tunnel. Each container has a virtual network adapter (vNIC) which is connected to a Hyper-V virtual switch (vSwitch). Windows containers function similarly to virtual machines in regards to networking.
This topic provides an overview of how Docker creates and manages host networks on Windows. However, the Windows and Linux network stacks are different, and as such you will find that some Linux network commands (for example, ifconfig) are not supported on Windows. With the exception of any cases described in unsupported features and network options, all Docker networking commands are supported on Windows with the same syntax as on Linux. Please reference Docker Container Networking for general Docker networking commands, options, and syntax.
0 kommentar(er)
