--alert-addr doesn't work
When specifying --alert-addr, usage is printed.
Applies to 0.5.0
Hmm, when I download the source and try with either master or tag v0.5.0 it works fine. The following does not though. docker run --rm -it acaleph/consul-alerts:latest start --alert-addr=localhost:9000
oh, ick. I see the problem. The entrypoint for the docker image runs --alert-addr
Do you think it needs a PR update to README to clarify or philosophically opposed to docker image config?
On Thu, Mar 7, 2019, 6:55 PM dbresson [email protected] wrote:
oh, ick. I see the problem. The entrypoint for the docker image runs --alert-addr
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/AcalephStorage/consul-alerts/issues/254#issuecomment-470785723, or mute the thread https://github.com/notifications/unsubscribe-auth/AIFVmvYr95O1egwyZJJ7owcqqEEvRyK_ks5vUdEcgaJpZM4bkaDw .
I don't think the docker image should be that way, but I don't see a way to change it without breaking backwards compatibility, and you guys only publish a "latest" tag.
I was able to work around it by overriding the entrypoint once I knew that was the issue, so an update to the documentation is probably sufficient.