Open snathanail opened 1 month ago
This issue has not had any activity in the past 30 days, so the needs-attention
label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention
label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!
What's wrong?
When spinning up a new container for Alloy, the server listens to 127.0.0.1:12345 rather than 0.0.0.0:12345. This causes the requests to http://localhost:12345 from outside the container to fail (ERR_EMPTY_RESPONSE from Chrome, error 52 from curl).
This has an easy fix, bind the listening IP address of the Alloy server to 0.0.0.0:12345 rather than 127.0.0.1:12345, and it will be solved. I mitigated that by adding the below line to the docker-compose.yml:
entrypoint: alloy run --server.http.listen-addr=0.0.0.0:12345 --storage.path=/var/lib/alloy/data /etc/alloy/config.alloy
but it should be set like that by default.Steps to reproduce
Also create a config.alloy as in the below configuration and save it under
/my-path-blah
System information
Windows 11 with Docker Desktop 4.33.1
Software version
Grafana Alloy v1.3
Configuration
Logs