elasticsearch 5.x vm.max_map_count issue alleviated, by docker-librar…

…y/elasticsearch#153, as pointed out by @matthiasnoback in #16

install-prerequisites.sh

@@ -23,12 +23,6 @@ echo "############################### Making docker-compose executable..."
 echo "------------------------------------------------------------"
 chmod +x /usr/local/bin/docker-compose
 
-echo "------------------------------------------------------------"
-echo "############################### Increases maximum memory map areas on host..."
-# This is a new requirement for Elasticsearch in 5.x, which HAS to be changed on the host and can not be accounted for on the image/container side of things. See https://github.com/docker-library/elasticsearch/issues/98 ...
-echo "------------------------------------------------------------"
-sudo sysctl -w vm.max_map_count=262144
-
 echo "------------------------------------------------------------"
 echo "############################### Installing apache2-utils so we have at our disposal htpasswd..."
 apt-get install apache2-utils -y --install-recommends

logging/docker-compose.yml

@@ -65,6 +65,7 @@ services:
     volumes:
       - ../storage/elasticsearch:/usr/share/elasticsearch/data
     restart: always
+    command: elasticsearch -Etransport.host=127.0.0.1
     labels:
       container_group: logging
     logging: