Note that you must use the name of the signature file, and you should use the one that's appropriate to the download you're verifying. To verify the authenticity of any downloaded data, grab both files and then run: gpg -verify geth-linux-amd64-1.5.asc Please note that this configuration exposes port 9200 on all network interfaces, and given how Docker manipulates iptables on Linux, this means that your Elasticsearch cluster is publically accessible, potentially ignoring any. Node es01 listens on localhost:9200 and es02 and es03 talk to es01 over a Docker network. Similarly you can import all the developer public keys by grabbing them directly from the keyserver network: gpg -recv-keys E058A81C 05A5DDF0 1CCB7DD2įrom the download listings above you should see a link both to the downloadable archives as well as detached signature files. This sample Docker Compose file brings up a three-node Elasticsearch cluster. You can import the build server public keys by grabbing the individual keys directly from the keyserver network: gpg -recv-keys F9585DE6 C2FF8BBF 9BA28146 7B9E2481 D2A67EAC
