Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upThe configuration values in Dockerfile should be the same as the default values #4029
Comments
This comment has been minimized.
This comment has been minimized.
|
This is a Docker usage question, we can't help you with that. |
brian-brazil
closed this
Mar 30, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
chihkaiyu commentedMar 30, 2018
This is not a bug.
When I run the Prometheus in docker, it's good and everything works properly.
Then I try to alter some configurations like TSDB data path, retention period, it says it can't load my configuration files (prometheus.yml).
After tracing the code a little bit, I know this is not a bug.
But I think it's much more intuitive if the configuration values in Dockerfile could be the same as default values.
What did you do?
I run a docker container via:
docker run -d --name prometheus -p 9090:9090 prom/prometheus:v2.1.0 --storage.tsdb.retention=90dWhat did you expect to see?
I expect that the Prometheus should load the configuration file from
/etc/prometheus/prometheus.ymlWhat did you see instead? Under which circumstances?
err="Error loading config couldn't load configuration (--config.file=prometheus.yml): open prometheus.yml: no such file or directory"Environment
Docker version: 17.09.0-ce
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
System information:
Linux 4.10.0-40-generic x86_64
Prometheus version:
v2.1.0
Logs: