We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello.
I tested against current (literally) latest docker image (no version?) and previous 1.4.1 and when provided ie. -port 9000 doesn't work.
-port 9000
I tried to change order how I provide arguments, but order of arguments wasn't the reason. Other CLI (-config, -queries, -service) work.
I tried even looking at source code and there doesn't seem anything wrong with it.
/bin/docker run \ --rm \ --name prometheus_sql \ -p 9000:9000 \ -v /data/prometheus_sql:/data \ dbhi/prometheus-sql:1.4.1 \ -port 9000 \ -config /data/config.yml \ -queries /data/queries.yml \ -service http://sqlagent:5000
^^^ Doesn't work
I found workaround by providing -e PROMSQL_PORT=9000 to docker run.
-e PROMSQL_PORT=9000
docker run
Because of the work around it is not any high priority issue, but wanted to report anyway.
The text was updated successfully, but these errors were encountered:
Might be because how entrypoint works in docker image ...
prometheus-sql/docker-entrypoint.sh
Line 22 in 5d25f92
Sorry, something went wrong.
Thanks for reporting. Will fix
71ef16b
No branches or pull requests
Hello.
I tested against current (literally) latest docker image (no version?) and previous 1.4.1 and when provided ie.
-port 9000
doesn't work.I tried to change order how I provide arguments, but order of arguments wasn't the reason. Other CLI (-config, -queries, -service) work.
I tried even looking at source code and there doesn't seem anything wrong with it.
^^^ Doesn't work
I found workaround by providing
-e PROMSQL_PORT=9000
todocker run
.Because of the work around it is not any high priority issue, but wanted to report anyway.
The text was updated successfully, but these errors were encountered: