Running `promtool` with * from the docker image doesn't behave the same way with snap about prometheus HOT 4 CLOSED

I doubt this will be seen by the right audience. Maybe it's more a request for the maintainers of the snap packages?

from prometheus.

@beorn7 Sorry maybe it wasn't clear. Snap is behaving as I would expect it to behave while the docker image is the one "misbehaving" here.

from prometheus.

This isn't really anything to do with the Docker image either, overriding --entrypoint on the Docker command line is tricky to get right, particularly as Docker supports a JSON format for multiple arguments in the Dockerfile, but not on the command line.

With:

docker run -v $PWD:/charm --entrypoint "/bin/promtool" prom/prometheus:latest 'check rules /charm/src/prometheus_alert_rules/*.rule'

The entire argument of check rules /charm/src/prometheus_alert_rules/*.rule is being passed as one argument, with no shell parsing it. For the globs to work a shell needs to be involved.

My suggestion to make globbing work as you expect is to map in the same path on the host as the container, i.e.:

docker run -v $PWD:$PWD --entrypoint "" prom/prometheus:latest promtool check rules $PWD/*.rule
Checking /home/dgl/foo.rule
  SUCCESS: 0 rules found

Then the globbing happens outside the container. This approach will continue working in the future as we may stop shipping a shell inside the container (i.e. use "distroless" containers).

from prometheus.

Looks like this is a usage question. I'll convert it to a discussion so that it stays around to help others.

from prometheus.