Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
docker_notes:docker [2025-03-02 Sun wk09 11:21] – [References] baumkp | docker_notes:docker [2025-06-21 Sat wk25 12:15] (current) – [Networks] baumkp | ||
---|---|---|---|
Line 126: | Line 126: | ||
* Then pull the latest portainer/ | * Then pull the latest portainer/ | ||
<code yaml> | <code yaml> | ||
+ | |||
+ | It would seem remote agents by default do not show out of date images, can be toggled on/off under '' | ||
Line 260: | Line 262: | ||
===reference=== | ===reference=== | ||
*[[https:// | *[[https:// | ||
+ | *[[https:// | ||
*Docker Docs | *Docker Docs | ||
*[[https:// | *[[https:// | ||
Line 286: | Line 289: | ||
* '' | * '' | ||
- Host (Appears on the host machine as if installed there, no separate network.) | - Host (Appears on the host machine as if installed there, no separate network.) | ||
- | | + | -If you use the host network mode for a container, that container' |
+ | | ||
+ | -The macvlan network assigns a unique MAC address to each container, making it appear to be a physical device on your network, just like a traditional virtual machine. The Docker daemon then routes the traffic to containers on the basis of their MAC address. It also allows you to assign an IP address from the same subnet in which the Docker host resides. This avoids the use of the host network, there is no NAT overhead, and you won't run into network performance issues. | ||
- MACVLAN (without subVLAN) this create a new ip address on the host machine | - MACVLAN (without subVLAN) this create a new ip address on the host machine | ||
* <code bash> | * <code bash> |