From 2ce44893f50bd3daf56b67e5b61c97559e028807 Mon Sep 17 00:00:00 2001
From: bjoernellens1 <64093272+bjoernellens1@users.noreply.github.com>
Date: Mon, 23 Oct 2023 14:06:12 +0200
Subject: [PATCH] Update docker-compose.yaml

---
 docker-compose.yaml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docker-compose.yaml b/docker-compose.yaml
index e97f54b..1a0ab70 100644
--- a/docker-compose.yaml
+++ b/docker-compose.yaml
@@ -27,6 +27,7 @@ services: # in docker compose, service are definitions of your docker containers
       # Allows graphical programs in the container.
       - /tmp/.X11-unix:/tmp/.X11-unix:rw
       - ${XAUTHORITY:-$HOME/.Xauthority}:/root/.Xauthority
+    network_mode: host # host networking makes life easier
 
         
   # The rest of this file is an example of how I used docker, docker-compose and buildx bake to fully automate image building for the Segway RMP-lite 220 robot platform.
@@ -50,8 +51,8 @@ services: # in docker compose, service are definitions of your docker containers
     stdin_open: true
     tty: true
     # Networking and IPC for ROS 2 --> uncomment those 2 entries if working with ros2, otherwise you might just delete this.
-    #network_mode: host # host networking makes life easier
-    #ipc: host # --> faster communications between containers
+    network_mode: host # host networking makes life easier
+    ipc: host # --> faster communications between containers
     
     # Needed to display graphical applications
     #privileged: true # Should only be set to true in development phase. This parameter is not neccessary needed, as it is very much possible to set the right access permissions first to only expose devices to the container I really want to access.