multimodal: Fixed the seaweed access

[sathyendranv]

Description

multimodal: Fixed the seaweed access when docker network in different subnet

Fixes # (issue) ITEP-88063, ITEP-88200

Any Newly Introduced Dependencies

No

How Has This Been Tested?

Yes

Checklist:

• I agree to use the APACHE-2.0 license for my code changes.
• I have not introduced any 3rd party components incompatible with APACHE-2.0.
• I have not included any company confidential information, trade secret, password or security token.
• I have performed a self-review of my code.

[Copilot]

Pull request overview

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

Changes:

• Update the user guide to use the nginx-proxied image-store URL for browsing stored images.
• Broaden SeaweedFS containers’ NO_PROXY/no_proxy CIDR from 172.18.0.0/16 to 172.16.0.0/12 in docker-compose.yml.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
manufacturing-ai-suite/industrial-edge-insights-multimodal/docs/user-guide/how-to-guides/how-to-access-s3-stored-images.md	Aligns “navigate to filer” instructions with the nginx /image-store access path.
manufacturing-ai-suite/industrial-edge-insights-multimodal/docker-compose.yml	Expands SeaweedFS NO_PROXY/no_proxy CIDR to cover more Docker subnet allocations.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

The NO_PROXY/no_proxy values here fully overwrite any existing ${no_proxy} passed from the host environment (unlike other services in this compose file). Consider appending ${no_proxy} so existing proxy bypass settings are preserved, and making the Docker CIDR portion configurable rather than hardcoding 172.16.0.0/12 (which is very broad and may unintentionally bypass proxies for non-Docker 172.16/12 networks).

[vkb1]

False positive

[Copilot]

The NO_PROXY/no_proxy values here fully overwrite any existing ${no_proxy} passed from the host environment (unlike other services in this compose file). Consider appending ${no_proxy} so existing proxy bypass settings are preserved, and making the Docker CIDR portion configurable rather than hardcoding 172.16.0.0/12 (which is very broad and may unintentionally bypass proxies for non-Docker 172.16/12 networks).

Suggested change

	- 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
	- NO_PROXY=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,${DOCKER_NO_PROXY_CIDR:-172.16.0.0/12},${no_proxy}
	- no_proxy=localhost,127.0.0.1,seaweedfs-master,seaweedfs-volume,seaweedfs-filer,seaweedfs-s3,${DOCKER_NO_PROXY_CIDR:-172.16.0.0/12},${no_proxy}

[Copilot]

The NO_PROXY/no_proxy values here fully overwrite any existing ${no_proxy} passed from the host environment (unlike other services in this compose file). Consider appending ${no_proxy} so existing proxy bypass settings are preserved, and making the Docker CIDR portion configurable rather than hardcoding 172.16.0.0/12 (which is very broad and may unintentionally bypass proxies for non-Docker 172.16/12 networks).

[vkb1]

False positive

[Copilot]

The NO_PROXY/no_proxy values here fully overwrite any existing ${no_proxy} passed from the host environment (unlike other services in this compose file). Consider appending ${no_proxy} so existing proxy bypass settings are preserved, and making the Docker CIDR portion configurable rather than hardcoding 172.16.0.0/12 (which is very broad and may unintentionally bypass proxies for non-Docker 172.16/12 networks).

[vkb1]

False positive