Skip to content
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

amtool accessible in docker image for alertmanager #1119

Closed
ajuszczak opened this issue Nov 23, 2017 · 1 comment
Closed

amtool accessible in docker image for alertmanager #1119

ajuszczak opened this issue Nov 23, 2017 · 1 comment

Comments

@ajuszczak
Copy link

What did you do?

I'd like to be able to use amtool within alert manager docker image to be able to verify configuration passed to docker image before I will push it to Nexus.

> docker run -it --entrypoint=amtool prom/alertmanager:latest

What did you expect to see?
Help message returned by amtool script.

What did you see instead? Under which circumstances?

Error, which says that specific command doesn't exist.

docker: Error response from daemon: oci runtime error: container_linux.go:265: starting container process caused "exec: \"amtool\": stat amtool: no such file or directory".

Please note that this is actually done right now in Prometheus image:

> docker run -it --entrypoint=promtool prom/prometheus:latest
usage: promtool <command> [<args>]

Available commands:
  check-config     validate configuration files for correctness
  check-metrics    validate metrics for correctness
  check-rules      validate rule files for correctness
  help             prints this help text
  version          print the version of this binary

Environment

  • System information:

Linux 4.9.49-moby x86_64

  • Alertmanager version:

alertmanager, version 0.11.0 (branch: HEAD, revision: 30dd042)
build user: root@3e103e3fc918
build date: 20171116-17:43:56
go version: go1.9.2

@Arnold1
Copy link

Arnold1 commented Nov 26, 2017

im also interested, is there a way to login to the running alertmanager container?

hh pushed a commit to ii/alertmanager that referenced this issue Oct 20, 2018
Rename promu no-cgo config to default promu name to avoid crossbuild
problems.

Signed-off-by: Ben Kochie <superq@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants