Differences

This shows you the differences between two versions of the page.

--- docker_notes:docker [2025-03-02 Sun wk09 11:22] – [reference] baumkp
+++ docker_notes:docker [2025-06-21 Sat wk25 12:15] (current) – [Networks] baumkp
@@ Line 126: / Line 126: @@
   * Then pull the latest portainer/agent: ''%%docker pull portainer/agent%%'', default is latest if version is not specified.
 <code yaml>docker run -d   -p 9001:9001   --name portainer_agent   --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/docker/volumes:/var/lib/docker/volumes portainer/agent</code>
+It would seem remote agents by default do not show out of date images, can be toggled on/off under ''Host > Setup "Show image up to date indicators for Stacks, Services and Containers"''
@@ Line 287: / Line 289: @@
     * ''docker network create network_named''
   - Host (Appears on the host machine as if installed there, no separate network.)
-  - MACVLAN
+    -If you use the host network mode for a container, that container's network stack isn't isolated from the Docker host (the container shares the host's networking namespace), and the container doesn't get its own IP-address allocated.
+  - MACVLAN
+    -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
       * <code bash>docker network create \