Closed arusuki closed 3 months ago
That makes sense to me. Thanks for the detailed explanation!
@holopin-bot @arusuki give-him-the-burg
Congratulations @arusuki, the maintainer of this repository has issued you a badge! Here it is: https://holopin.io/claim/clz8ozi2k89330cjsu7o6pwrc
This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!
LRR Version and OS LRRVersion: 0.9.21 OS: Synology DSM 7.1-42661 Installation method: Docker Container
Summary The LRR container uses
wget
to check its health status, while thewget
shipped with alpine image is from busybox which does not respect theno_proxy
environment variable.Therefore, when
http_proxy
andhttps_proxy
environment variables are set, the wget command launched by docker health check uses proxy to accesshttp://localhost:3000
and fails the test. Thedocker ps
command therefore reports LRR container in unhealthy state which is false positive.Possible Solutions
apk add wget
to Dockerfile, which installs GNU wget which understandsno_proxy
, or-Y off
option to wget command to force busybox wget ignoring proxies when performing health check.To Reproduce
When
http_proxy
andhttps_proxy
environment variables are set, commanddocker ps
shows the LRR container in unhealthy states.To verify further, running command
docker exec -it <LRR container ID> sh
gives a shell in LRR container, then test thewget
used by health check.