-
-
Notifications
You must be signed in to change notification settings - Fork 394
Container reports "unhealthy" when specifying "LISTEN_ADDR" #1532
Copy link
Copy link
Closed
Labels
Waiting for reply⏳Waiting for the original poster to respond, or discussion in progress.Waiting for the original poster to respond, or discussion in progress.bug 🐛Something isn't workingSomething isn't workingnext release/in dev image 🚀This is coming in the next release or was already released if the issue is Closed.This is coming in the next release or was already released if the issue is Closed.
Metadata
Metadata
Assignees
Labels
Waiting for reply⏳Waiting for the original poster to respond, or discussion in progress.Waiting for the original poster to respond, or discussion in progress.bug 🐛Something isn't workingSomething isn't workingnext release/in dev image 🚀This is coming in the next release or was already released if the issue is Closed.This is coming in the next release or was already released if the issue is Closed.
What installation are you running?
Production (netalertx) 📦
Is there an existing issue for this?
The issue occurs in the following browsers. Select at least 2.
Current Behavior
Docker container reports "unhealthy" when specifying "LISTEN_ADDR"
This is caused by this using "localhost", which fails when not listening on "0.0.0.0".
Patching the above line as follows appears to resolve the issue, with the status reporting "healthy".
Expected Behavior
The status should report as "healthy"
Steps To Reproduce
docker ps)Relevant
app.confsettingsdocker-compose.yml
Debug or Trace enabled
Relevant
app.logsectionN/A
Docker Logs