Unset the proxy when performing the seaweedfs health check

[SteppingHat]

This PR includes a fix for running Sentry behind a proxy #3958 where the health check for the seaweedfs container is routed through the proxy due to wget not respecting the no_proxy header.

This issue was seen earlier with the clickhouse container, and this fix mimics the solution used to resolve the issue.

By appending the health check command with http_proxy='', requests to the seaweedfs endpoints are no longer routed through the proxy, allowing the Sentry stack to be installed behind a proxy as this caused the health check to fail otherwise, preventing the stack from being installed.

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

[aldy505]

Curious on why you dropped -q -O-. But overall, looks solid!

[SteppingHat]

This is a copy paste from my env which I dropped for testing. I seem to have forgotten to put it back, but thanks for pointing it out! I'll put it back in

[aldy505]

Integration test error:

  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
  yes: standard output: Broken pipe
  yes: standard output: Broken pipe
  -> ./install.sh:main:39
  --> install/bootstrap-s3-nodestore.sh:source:3
  

I assume wrong healthcheck command?

[SteppingHat]

@aldy505 probably was due to the related comment with the missing -q -O-. I checked out in a separate repo, applied the change and built the stack and all seems to be good, the tests should pass this time round.

[aldy505]

@aldy505 probably was due to the related comment with the missing -q -O-. I checked out in a separate repo, applied the change and built the stack and all seems to be good, the tests should pass this time round.

Okay. Just approved the CI run, let's see.

[aminvakil]

Thanks for fixing this!

[BYK]

There's an incident going on with Docker Hub which is the cause of all these failures: https://www.dockerstatus.com/pages/incident/533c6539221ae15e3f000031/68d47a2f93c09e05486d93a9

Will retry once that's fixed.

[SteppingHat]

There's an incident going on with Docker Hub which is the cause of all these failures: https://www.dockerstatus.com/pages/incident/533c6539221ae15e3f000031/68d47a2f93c09e05486d93a9

Will retry once that's fixed.

Looks like it's resolved 😄