You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 the wget shipped with alpine image is from busybox which does not respect the no_proxy environment variable.
Therefore, when http_proxy and https_proxy environment variables are set, the wget command launched by docker health check uses proxy to access http://localhost:3000 and fails the test. The docker ps command therefore reports LRR container in unhealthy state which is false positive.
Possible Solutions
add apk add wget to Dockerfile, which installs GNU wget which understands no_proxy, or
add -Y off option to wget command to force busybox wget ignoring proxies when performing health check.
To Reproduce
When http_proxy and https_proxy environment variables are set, command docker ps shows the LRR container in unhealthy states.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS
3a9f9661f76d difegue/lanraragi:latest "//init" 59 minutes ago Up 23 minutes (unhealthy) 0.0.0.0:3000->3000/tcp
To verify further, running command docker exec -it <LRR container ID> sh gives a shell in LRR container, then test the wget used by health check.
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.The text was updated successfully, but these errors were encountered: