Différences

Ci-dessous, les différences entre deux révisions de la page.

--- cours:iot:node-red_on_docker [2019/01/16 10:30] – [Mosquitto Installation in a second container] tigli
+++ cours:iot:node-red_on_docker [2019/01/28 18:22] (Version actuelle) – [Network Management in Docker] tigli
@@ Ligne 60: / Ligne 60: @@
 == Caveats : Docker Containers Mosquitto Configuration ==
-{{ :cours:iot:hostname-port_configuration.png | 200}}
+{{ :cours:iot:hostname-port_configuration.png?500 |}}
-=== Caveats : Docker Containers Network Configuration ====
+== Containers Network configuration for docker and its containers ==
+// They in bridge mode and disconnect to host network // in the following steps.
+The result is described in the figure bellow.
+==== Caveats : Docker Containers Network Configuration ====
 {{ :cours:iot:docker_containers_network.jpg?700 |}}
@@ Ligne 69: / Ligne 75: @@
 [[http://mqttfx.org/|JavaFX based MQTT Client]]
+The GUI client is running on the native computer, so the access to the mosquitto broker is done through // localhost:2500  // in this case (see above).
 === Test Shell MQTT Clients ===
 docker run -it ubuntu bash
+If the clients are running on the native computer, the access to the mosquitto broker is done through // localhost:2500  // in this case (see above).
 === Test with Node-Red in a Docker Container ===
+Because Node-Red is running in a Docker container, the MQTT client nodes can access to the mosquitto broker through //172.17.0.1// (the gateway address) in our case.
+===== Appendices =====
+==== Network Management in Docker ====
+[[https://blog.docker.com/2016/12/understanding-docker-networking-drivers-use-cases/|understanding docker networking drivers use cases]]
+[[cours:iot:network_management_in_docker|Network in Docker]]
+====== Solutions ======
+{{:cours:iot:solution_node_red_and_mosquitto_clients.rtf|}}