Failing to Build -- release artifacts modified? about aerospike-server.docker

[volmarl]

Thanks for bringing this up. Our build systems had a glitch that got resolved. Let me update the offcial repo.

[tianon]

Running ./update.sh gives me the following SHA256 change, but IMO this change ought to be looked into as well (to make sure we know why the bits on the server changed):

diff --git a/Dockerfile b/Dockerfile
index 8cfa5ea..cb13c6d 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -7,7 +7,7 @@
 FROM ubuntu:xenial
 
 ENV AEROSPIKE_VERSION 3.11.0.2
-ENV AEROSPIKE_SHA256 a6dfff8d278f628ca681ec92cdefaef9f8a7c534e5c9feece5060ac7d3b65453            
+ENV AEROSPIKE_SHA256 3ede8b3232a8ca0f0e34f2eb9f37fa244dc502020f2d185f96ee3097d88cda21
 
 # Install Aerospike Server and Tools
 

[tianon]

Might also be worth pointing out that update.sh appears to scrape the sha256 value from aerospike-server-community-${fullVersion}-debian7.tgz.sha256, while the Dockerfile actually downloads aerospike-server-community-${fullVersion}-ubuntu16.04.tgz (not sure whether that's actually relevant, simply an observation).