-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
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
Push the simple and random examples to docker hub #347
Comments
I don't feel strongly. @discordianfish does this make sense? |
Sounds good! |
When those are published on Dockerhub, people will be able to start those examples in fewer steps than the current documentation: https://prometheus.io/docs/introduction/getting_started/#starting-up-some-sample-targets While relying on Docker may not be always wished, giving the possibility to quickly start a daemon that exposes metrics can be useful in many tutorials. This commit tries really hard to limit the number of per-example maintenance work by sharing most of the Makefile to build the Docker images. The tiny top level Makefiles in each example directory are strictly identical. Updates: prometheus#347
When those are published on Dockerhub, people will be able to start those examples in fewer steps than the current documentation: https://prometheus.io/docs/introduction/getting_started/#starting-up-some-sample-targets While relying on Docker may not be always wished, giving the possibility to quickly start a daemon that exposes metrics can be useful in many tutorials. The simple and random example are build as static binaries and packaged as single binaries in Docker images. This commit tries really hard to limit the number of per-example maintenance work by sharing most of the Makefile to build the Docker images. The tiny top level Makefiles in each example directory are strictly identical. Updates: prometheus#347
When those are published on Dockerhub, people will be able to start those examples in fewer steps than the current documentation: https://prometheus.io/docs/introduction/getting_started/#starting-up-some-sample-targets While relying on Docker may not be always wished, giving the possibility to quickly start a daemon that exposes metrics can be useful in many tutorials. The simple and random example are build as static binaries and packaged as single binaries in Docker images. This commit tries really hard to limit the number of per-example maintenance work by sharing most of the Makefile to build the Docker images. The tiny top level Makefiles in each example directory are strictly identical. Updates: prometheus#347
When those are published on Dockerhub, people will be able to start those examples in fewer steps than the current documentation: https://prometheus.io/docs/introduction/getting_started/#starting-up-some-sample-targets While relying on Docker may not be always wished, giving the possibility to quickly start a daemon that exposes metrics can be useful in many tutorials. The simple and random example are build as static binaries and packaged as single binaries in Docker images. This commit tries really hard to limit the number of per-example maintenance work by sharing most of the Makefile to build the Docker images. The tiny top level Makefiles in each example directory are strictly identical. Updates: prometheus#347
When those are published on Dockerhub, people will be able to start those examples in fewer steps than the current documentation: https://prometheus.io/docs/introduction/getting_started/#starting-up-some-sample-targets While relying on Docker may not be always wished, giving the possibility to quickly start a daemon that exposes metrics can be useful in many tutorials. The simple and random example are build as static binaries and packaged as single binaries in Docker images. This commit tries really hard to limit the number of per-example maintenance work by sharing most of the Makefile to build the Docker images. The tiny top level Makefiles in each example directory are strictly identical. Updates: prometheus#347
When those are published on Dockerhub, people will be able to start those examples in fewer steps than the current documentation: https://prometheus.io/docs/introduction/getting_started/#starting-up-some-sample-targets While relying on Docker may not be always wished, giving the possibility to quickly start a daemon that exposes metrics can be useful in many tutorials. The simple and random example are build as static binaries and packaged as single binaries in Docker images. This commit tries really hard to limit the number of per-example maintenance work by sharing most of the Makefile to build the Docker images. The tiny top level Makefiles in each example directory are strictly identical. Updates: prometheus#347
Whats the state on this? I would love to use those images in our Grafana dev environment. Yes. I'm to lazy to build them myself ;) |
See discussion on #348 . It looks we need to implement what was suggested last in the discussion on that (already merged) PR. I wanted to do it, but I have to admit I have way too many things on my plate that are much more important. |
…theus#347) Signed-off-by: Pedro Sland <[email protected]>
Move both examples into single Dockerfile for Docker Hub (fixes #347)
It'd be nice to be able to install those two examples with docker invocations so both an instrumented daemon and prometheus can be started this way. This would allow a full end to end example with two
docker run
and with a config file bound mounted, which seems fairly minimal.The labels could be:
prometheus/example-golang-simple
prometheus/example-golang-random
I can prepare a PR building the docker images, but would be good to know if people are happy with the idea.
The text was updated successfully, but these errors were encountered: