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 upprometheus docker does crash Exited (1) when insecure_skip_verify is set to true #3657
Comments
This comment has been minimized.
This comment has been minimized.
|
Check your indentation. It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided. |
brian-brazil
closed this
Jan 5, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 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 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
arunvsankar commentedJan 5, 2018
•
edited by brian-brazil
What did you do?
I am trying to integrate jenkins with prometheus. I installed a prometheus plugin in jenkins. The jenkins has an invalid certificate.

I see the docker image does not start but fails with exit(1) status code.
What did you expect to see?
What did you see instead? Under which circumstances?
In order to skip the verification, I tried to add insecure_skip_verify as true in prometheus.yml file and start the docker container on prometheus.
When i restart the prometheus docker image, the container does not start but throws an Exited(1) and would not start
9f26831ba90d prom/prometheus "/bin/prometheus -sto" 10 weeks ago Exited (1) 4 seconds ago prometheus
Environment
I use a RHEL
Linux 4.4.0-97-generic x86_64
Prometheus version:
prom/prometheus latest 03f045a7680f
Alertmanager version:
insert output of
alertmanager --versionhere (if relevant to the issue)Prometheus configuration file: