multimodal: Fixed the seaweed access issue (#2022)

Updates multimodal’s SeaweedFS access path and proxy bypass configuration
so image browsing works reliably when the Docker network uses a different subnet.

Signed-off-by: Vellaisamy, Sathyendran <sathyendran.vellaisamy@intel.com>

Author: sathyendranv

manufacturing-ai-suite/industrial-edge-insights-multimodal/docker-compose.yml

@@ -430,8 +430,8 @@ services:
     volumes:
       - seaweed_master_data:/data
     environment:
-      - NO_PROXY=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.18.0.0/16
-      - no_proxy=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.18.0.0/16
+      - NO_PROXY=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.16.0.0/12
+      - no_proxy=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.16.0.0/12
     command: master -ip=seaweedfs-master -ip.bind=0.0.0.0
 
   seaweedfs-volume:
@@ -449,8 +449,8 @@ services:
     volumes:
       - seaweed_volume_data:/data
     environment:
-      - NO_PROXY=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.18.0.0/16
-      - no_proxy=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.18.0.0/16
+      - NO_PROXY=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.16.0.0/12
+      - no_proxy=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.16.0.0/12
     command: volume -mserver=seaweedfs-master:9333 -ip.bind=0.0.0.0 -port=8080
     depends_on:
       - seaweedfs-master
@@ -469,8 +469,8 @@ services:
       - seaweed_filer_data:/data
       - "vol_temp_seaweed_filer:/tmp"
     environment:
-      - NO_PROXY=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.18.0.0/16
-      - no_proxy=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.18.0.0/16
+      - NO_PROXY=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.16.0.0/12
+      - no_proxy=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.16.0.0/12
     command: filer -master=seaweedfs-master:9333 -ip.bind=0.0.0.0
     depends_on:
       - seaweedfs-master
@@ -495,8 +495,8 @@ services:
     networks:
       - timeseries_network
     environment:
-      - NO_PROXY=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.18.0.0/16
-      - no_proxy=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.18.0.0/16
+      - NO_PROXY=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.16.0.0/12
+      - no_proxy=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,172.16.0.0/12
       # Comma-separated list of default buckets to create
       - DEFAULT_S3_BUCKETS=dlstreamer-pipeline-results
       # S3 credentials from .env file

manufacturing-ai-suite/industrial-edge-insights-multimodal/docs/user-guide/how-to-guides/how-to-access-s3-stored-images.md

@@ -64,7 +64,7 @@ Follow these steps to correlate detection events in InfluxDB with stored images:
 3. Navigate to the Filer interface:
 
    ```text
-   http://<host_ip>:8887/buckets/dlstreamer-pipeline-results/weld-defect-classification/
+   https://<host_ip>:3000/image-store/buckets/dlstreamer-pipeline-results/weld-defect-classification/
    ```
 
 4. Locate and open the file matching the `img_handle` (e.g., `X7TINNVPNX.jpg`).