Cannot install or run sentry with seaweedfs behind a proxy

[SteppingHat]

Self-Hosted Version

25.9.0

CPU Architecture

x86_64

Docker Version

28.4.0

Docker Compose Version

2.39.2

Machine Specification

• My system meets the minimum system requirements of Sentry

Steps to Reproduce

1. Set the http_proxy, https_proxy and no_proxy environment as per the Sentry and docker configuration when configuring an instance behind a proxyhttps://develop.sentry.dev/self-hosted/#installing-behind-a-proxy
2. Run the install script as per usual

This is on a clean system, fresh install of docker and OS and no prior Sentry installation.

Expected Result

Sentry should be able to install with no issues.

Actual Result

What will happen is that the health check for seaweedfs will fail after it's timeout and abort the installation.

Docker images built.

▶ Bootstrapping seaweedfs (node store)...
 Network sentry-self-hosted_default  Creating
 Network sentry-self-hosted_default  Created
 Container sentry-self-hosted-postgres-1  Creating
 Container sentry-self-hosted-seaweedfs-1  Creating
 Container sentry-self-hosted-postgres-1  Created
 Container sentry-self-hosted-seaweedfs-1  Created
 Container sentry-self-hosted-postgres-1  Starting
 Container sentry-self-hosted-seaweedfs-1  Starting
 Container sentry-self-hosted-postgres-1  Started
 Container sentry-self-hosted-seaweedfs-1  Started
 Container sentry-self-hosted-seaweedfs-1  Waiting
 Container sentry-self-hosted-postgres-1  Waiting
 Container sentry-self-hosted-postgres-1  Healthy
container sentry-self-hosted-seaweedfs-1 is unhealthy
Error in install/bootstrap-s3-nodestore.sh:3.
'$dc up --wait seaweedfs postgres' exited with status 1
-> ./install.sh:main:39
--> install/bootstrap-s3-nodestore.sh:source:3

This issue seems similar to #1537 where the instance of wget used in the health check does not respect the no_proxy environment variable, and the requests made to seaweedfs are being passed through the proxy, causing the heath check to fail.

Event ID

No response

[SteppingHat]

Opened up a PR to resolve this - see #3959