pkhander/compose-prometheus

Deploy Promethues + Grafana + SNMP exporter using docker-compose

compose-prometheus's Issues

Try to create compose-generator.yml

root@grafana:/opt/containers/compose-prometheus# docker-compose -f compose-generator.yml up
Recreating compose-prometheus_snmp-generator_1 ... error

ERROR: for compose-prometheus_snmp-generator_1 Cannot start service snmp-generator: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: process_linux.go:458: setting cgroup config for procHooks process caused: can't load program: operation not permitted: unknown

ERROR: for snmp-generator Cannot start service snmp-generator: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: process_linux.go:458: setting cgroup config for procHooks process caused: can't load program: operation not permitted: unknown
ERROR: Encountered errors while bringing up the project.

Suggestions for docker-compose.yml

In the configuration for the snmp exporter:

compose-prometheus/docker-compose.yml

Lines 25 to 35 in cf076f2

	snmp-exporter:
	image: prom/snmp-exporter
	volumes:
	- ./snmp_exporter/:/etc/snmp_exporter/
	expose:
	- 9116
	ports:
	- 9116:9116
	- 116:116/udp
	networks:
	- public

It's not necessary to use the expose directive. This is almost never necessary, and you're not using it on your other containers.

I don't think you need to publish UDP port 116, either. What service is using that port?

Lastly, I don't think you even need to publish tcp port 9116 for this container. It only needs to be reachable from the prometheus container, which since it is on the same network will be able to access the service regardless of whether or not it is published.