Docker 2024 04/Networking: Unterschied zwischen den Versionen

Aus CCWiki
Zur Navigation springen Zur Suche springen
Zum nächsten Versionsunterschied →
Drlue (Diskussion | Beiträge)
Bürokraten, Oberflächenadministratoren, Administratoren
2.987 Bearbeitungen
Die Seite wurde neu angelegt: „Folgendes soll einen Grundlegenden Überblick über das Container Networking bieten. === Netzwerk Typen === Docker verwendet für die Netzwerkkommunikation Treiber. Folgende Treiber sind Standardmäßig Verfügbar. Im folgenden werden wir uns auf die Netzwerktypen '''Host''' und '''Bridge''' beschränken. '''bridge:''' The default network driver. If you don't specify a driver, this is the type of network you are creating. Bridge networks are commonly…“
 
Keine Bearbeitungszusammenfassung
Zeile 4: Zeile 4:
Docker verwendet für die Netzwerkkommunikation Treiber. Folgende Treiber sind Standardmäßig Verfügbar. Im folgenden werden wir uns auf die Netzwerktypen '''Host''' und '''Bridge''' beschränken.
Docker verwendet für die Netzwerkkommunikation Treiber. Folgende Treiber sind Standardmäßig Verfügbar. Im folgenden werden wir uns auf die Netzwerktypen '''Host''' und '''Bridge''' beschränken.


  '''bridge:''' The default network driver. If you don't specify a driver, this is the type of network you are creating. Bridge networks are commonly used when your application runs in a container that needs to  
'''bridge:''' The default network driver. If you don't specify a driver, this is the type of network you are creating. Bridge networks are commonly used when your application runs in a container that needs to communicate with other containers on the same host.
  communicate with other containers on the same host.


  host: Remove network isolation between the container and the Docker host, and use the host's networking directly.
'''host:''' Remove network isolation between the container and the Docker host, and use the host's networking directly.


  '''overlay:''' Overlay networks connect multiple Docker daemons together and enable Swarm services and containers to communicate across nodes. This strategy removes the need to do OS-level routing.
'''overlay:''' Overlay networks connect multiple Docker daemons together and enable Swarm services and containers to communicate across nodes. This strategy removes the need to do OS-level routing.


  '''ipvlan:''' IPvlan networks give users total control over both IPv4 and IPv6 addressing. The VLAN driver builds on top of that in giving operators complete control of layer 2 VLAN tagging and even IPvlan L3 routing for users interested in underlay network integration.
'''ipvlan:''' IPvlan networks give users total control over both IPv4 and IPv6 addressing. The VLAN driver builds on top of that in giving operators complete control of layer 2 VLAN tagging and even IPvlan L3 routing for users interested in underlay network integration.


  '''macvlan:''' Macvlan networks allow you to assign a MAC address to a container, making it appear as a physical device on your network. The Docker daemon routes traffic to containers by their MAC addresses. Using the macvlan driver is sometimes the best choice when dealing with legacy applications that expect to be directly connected to the physical network, rather than routed through the Docker host's network stack.
'''macvlan:''' Macvlan networks allow you to assign a MAC address to a container, making it appear as a physical device on your network. The Docker daemon routes traffic to containers by their MAC addresses. Using the macvlan driver is sometimes the best choice when dealing with legacy applications that expect to be directly connected to the physical network, rather than routed through the Docker host's network stack.


  '''none:''' Completely isolate a container from the host and other containers. none is not available for Swarm services.
'''none:''' Completely isolate a container from the host and other containers. none is not available for Swarm services.
<ref>https://docs.docker.com/network/drivers/</ref>
<ref>https://docs.docker.com/network/drivers/</ref>

Version vom 12. April 2024, 10:58 Uhr

Folgendes soll einen Grundlegenden Überblick über das Container Networking bieten.

Netzwerk Typen

Docker verwendet für die Netzwerkkommunikation Treiber. Folgende Treiber sind Standardmäßig Verfügbar. Im folgenden werden wir uns auf die Netzwerktypen Host und Bridge beschränken. 

bridge: The default network driver. If you don't specify a driver, this is the type of network you are creating. Bridge networks are commonly used when your application runs in a container that needs to communicate with other containers on the same host.

host: Remove network isolation between the container and the Docker host, and use the host's networking directly.

overlay: Overlay networks connect multiple Docker daemons together and enable Swarm services and containers to communicate across nodes. This strategy removes the need to do OS-level routing.

ipvlan: IPvlan networks give users total control over both IPv4 and IPv6 addressing. The VLAN driver builds on top of that in giving operators complete control of layer 2 VLAN tagging and even IPvlan L3 routing for users interested in underlay network integration.

macvlan: Macvlan networks allow you to assign a MAC address to a container, making it appear as a physical device on your network. The Docker daemon routes traffic to containers by their MAC addresses. Using the macvlan driver is sometimes the best choice when dealing with legacy applications that expect to be directly connected to the physical network, rather than routed through the Docker host's network stack.

none: Completely isolate a container from the host and other containers. none is not available for Swarm services.

[1]

  1. ↑ https://docs.docker.com/network/drivers/
Abgerufen von „https://ccwiki.digitalcampusvorarlberg.at/index.php?title=Docker_2024_04/Networking&oldid=3336“