Issues with pasta settings and podman network #23697
Unanswered
matteo-gambarutti
asked this question in
Q&A
Replies: 1 comment
-
This diagram #22943 (comment) shows what happens when you create a custom network and connect that with user-mode networking. Once you have that, you can't refer to "the host" using a loopback address anymore: you need to use a local (not loopback!) address that's configured on the host. |
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.
-
I'm trying to implement the Grafana-Prometheus-Node-exporter stack with podman. Grafana and Prometheus are containers whereas node_exporter is not.
I'd like to have both Grafana and Prometheus in the same podman network so I use containers names.
Node_exporter exposes port 9100.
In the prometheus quadlet file, I can specify
Network=pasta:-T,9100-9100
and with this I can refer to node_exporter with localhost because of the port forwarding. However, I also need to join a podman network calledgp.network
.So I changed that line to
Network=gp.network
and moved the pasta settings to~/.config/containers/containers.conf.d/0_network.conf
with the following content:With these settings I can't access the metrics of node_exporter from Prometheus and even I can't access Prometheus from Grafana using the container name nor using the host IP address.
Is what I'm trying to achieve possible? What am I doing wrong?
Beta Was this translation helpful? Give feedback.
All reactions