The updates to the Dockerfile are to help cleanup the deb and deps, as well as increase "security" by embedding the SHA into the dockerfile (the update script in the second commit will help keep this in sync with the version).
The update script uses https://www.aerospike.com/artifacts/aerospike-server-community/ to find the newest version of aerospike so that you only have to ./update.sh, git add -p. and git commit when an version bump is needed.
The generate-stackbrew-library.sh is to help in creating the PR to official-images. Once you commit a version bump or other updates to aerospike, just run ../aerospike-server.docker/generate-stackbrew-library.sh > library/aerospike from you clone of official-images (adjusting relative path as necessary). I also included a commented out section if you want to have aliases of 3 and 3.4 for 3.4.1 (which will naturally follow 3.4.x when released).
The updates to the Dockerfile are to help cleanup the deb and deps, as well as increase "security" by embedding the SHA into the dockerfile (the update script in the second commit will help keep this in sync with the version).
The update script uses
https://www.aerospike.com/artifacts/aerospike-server-community/to find the newest version of aerospike so that you only have to./update.sh,git add -p. andgit commitwhen an version bump is needed.The
generate-stackbrew-library.shis to help in creating the PR to official-images. Once you commit a version bump or other updates to aerospike, just run../aerospike-server.docker/generate-stackbrew-library.sh > library/aerospikefrom you clone of official-images (adjusting relative path as necessary). I also included a commented out section if you want to have aliases of3and3.4for3.4.1(which will naturally follow 3.4.x when released).