Open jperville opened 7 years ago
===> Compiling gpb
/usr/lib/erlang/lib/parsetools-2.1.4/include/leexinc.hrl: no such file or directory
===> Compiling /usr/src/prometheus_process_collector/_build/default/plugins/gpb/src/gpb_scan.xrl failed
/usr/lib/erlang/lib/parsetools-2.1.4/include/leexinc.hrl:none: no such file or directory
Looks like erlang sources are needed to build gpb.
But it won't be enough to build ez archive loadable by rabbitmq. But since it's archive maybe you can try to replace *.so manually. if not, I'll add Rabbitmq-specific Makefile here or to prometheus_rabbitmq_exporter. Also, please note that I forgot to update prometheus version here :-).
I'll be interested if you can fix my Dockerfile and commit it as example in this repository.
:-) Actually this sounds like a good idea (to have Dockerfile here) because people have all sorts of problems with glibc incompatibilities.
We can build code archives with rebar3 archive
. This command will produce *.ez archive that can be used with rabbitmq. So you can build it in your environment. Please let me know how it went.
I bumped prometheus.erl version. It no longer requires gpb in default rebar3 profile. should be buildable now.
Hi @deadtrickster , can you document how to build the plugin so that it can be installed with a specific version of the RabbitMQ docker image? I need to build the plugin because of your last comment https://github.com/deadtrickster/prometheus_rabbitmq_exporter/issues/12#issuecomment-290684007
I tried to run
./rebar3 build
as explained in the README.md, but I think I am missing some dependencies. Read on for how to reproduce.I have written this Dockerfile:
When I build the image, the "rebar3 compile" step fails with the following messages:
The full
docker build
trace is below: