anchor.diff: -= Java tests with Elasticsearch 5.0
  += Testing a Java and Elasticsearch 5.0 application
   :hp-tags: elasticsearch
   :published_at: 2016-11-29
   :hp-image: /images/logos/elasticsearch.png
  
positive.code: ----
  
  If you don't have sufficient privileges to change such setting, then you're in trouble.
  I personally missing a setting to be able to disable bootstrap checking.
  
negative.code: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
  ----
  
  When Elasticsearch 5.0 is running inside a Docker container, it has to listen on a Docker interface, not localhost.
  This network setting makes Elasticsearch think it is running in production mode.
  As a consequence, Elasticsearch does some additional https://www.elastic.co/blog/bootstrap_checks_annoying_instead_of_devastating[bootstrap checks] to avoid common production issues.
  Like on your production server, you'll have to do some the system level tuning to allow it to start:
  
  