node_exporter: no such file or directory when starting the latest docker image
There is an issue with latest build. (I’m sure, I tested different servers)
The last test I did, I actually had a working version of node_exporter, and after a pull, I see the error:
core@## ~ $ docker run prom/node-exporter
time="2016-11-26T18:25:16Z" level=info msg="Starting node_exporter (version=0.12.0, branch=master, revision=df8dcd2)" source="node_exporter.go:135"
time="2016-11-26T18:25:16Z" level=info msg="Build context (go=go1.6.2, user=root@ff68505a5469, date=20160505-22:14:18)" source="node_exporter.go:136"
time="2016-11-26T18:25:16Z" level=info msg="No directory specified, see --collector.textfile.directory" source="textfile.go:57"
time="2016-11-26T18:25:16Z" level=info msg="Enabled collectors:" source="node_exporter.go:155"
time="2016-11-26T18:25:16Z" level=info msg=" - uname" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - vmstat" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - conntrack" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - entropy" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - mdadm" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - sockstat" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - loadavg" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - netdev" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - textfile" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - time" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - netstat" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - stat" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - diskstats" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - filefd" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - filesystem" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg=" - meminfo" source="node_exporter.go:157"
time="2016-11-26T18:25:16Z" level=info msg="Listening on :9100" source="node_exporter.go:176"
^Ccore@## ~ $ docker pull prom/node-exporter
Using default tag: latest
latest: Pulling from prom/node-exporter
8ddc19f16526: Already exists
a3ed95caeb02: Pull complete
8279f336cdd3: Already exists
3b3ac81f79ba: Pull complete
Digest: sha256:ef2b36623fdeecbc4c58e189b54327b4595c2c066c4c6ca7bc6834c6916b2137
Status: Downloaded newer image for prom/node-exporter:latest
core@## ~ $ docker run prom/node-exporter
no such file or directory
docker: Error response from daemon: Cannot start container a2740f1ed2e9e128ab8e49403b18c470de5aa92512948d6e32ee5aa1fbe29123: [9] System error: json: cannot unmarshal object into Go value of type libcontainer.syncType.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 1
- Comments: 15 (8 by maintainers)
Because the build and push is fully automatic. The binaries themselves are not broken, but the container image causes issues. We’ve found the build bug that causes the binary to be built dynamically, instead of statically (the root cause of the problem).
Next up, add some better regression tests to the docker build.
@SuperQ I will take a look this evening.
Confirming this: