Replies: 1 comment
-
looks like i may have been going down the wrong path here, just ran defaults:
with flags:
pardon the confusion. this was an early test before setting up a compose file which i imagine will sort this all out anyways? just out of curiosity is there an option i missed to keep the default arguments when specifying an additional argument? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
hello,
i'm testing a prometheus container with
-v
bind mounts using:this seems to work fine and after some testing i ran
$ podman stop prometheus && podman rm prometheus
and then tried the abovepodman run
command with the prometheus--web.enable-admin-api
command line flag appended to the end. the container immediately stopped and the log shows the errorts=2024-10-02T17:47:26.921Z caller=main.go:549 level=error msg="Error loading config (--config.file=prometheus.yml)" file=/prometheus/prometheus.yml err="open prometheus.yml: no such file or directory"
. additionally appending--config.file=/etc/prometheus/prometheus.yml
appears to resolve the error, but theprometheus-data
volume didn't appear to be mounted in the running container.in other words
podman run
...docker.io/prom/prometheus
mounts the specified-v
file and volume without an issue.podman run
...docker.io/prom/prometheus --web.enable-admin-api
with the same-v
options doesn't seem to create the bind mounts?i tried reading through the man pages for
podman run
to see if this is expected behavior. not sure if i missed something obvious, but posting here in the hopes of clarifying what's happening.thanks
Beta Was this translation helpful? Give feedback.
All reactions