anchor.diff:  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 Docker interface, not localhost.
  -This network setting make Elasticsearch think it is running in production mode.
  +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:
   
  
positive.code: sleep 10s
  curl "http://localhost:9200/_cluster/health?wait_for_status=yellow&timeout=30s" # <4>
  ----
  <1> Download Elasticsearch. We could download it from a corporate repository (Nexus, web server...).
  <2> Unzip the downloaded archive.
  <3> Start Elasticsearch as a background process and keep it's PID so as to be able to stop it at the end.
  <4> Wait for Elasticsearch to be up and running.
  
  The drawback of this script is that it can not run on Windows.
  We could rewrite it using Ant, https://github.com/elastic/elasticsearch/blob/5.0/dev-tools/smoke_test_rc.py[Python] or Groovy/Gradle to make it more portable:
  
  [source,xml]
  .build.xml
  
negative.code: ----
  Starting with Elasticsearch 5.0, it's https://www.elastic.co/blog/elasticsearch-the-server#_embedded_elasticsearch_not_supported[forbidden to start an embedded Elasticsearch].
  The `NodeBuilder` class used above doesn't exist anymore, and most of classes used to start Elasticsearch as a server are hidden and sealed.
  In short, it's not as easy as before to test your Elasticsearch access layer, Java developers have lost their advantage of using the same language as Elasticsearch.
  Most solutions described in this article can probably apply to other languages: Ruby, Python, JavaScript...
  
  Let's see which options are left.
  
  == Elasticsearch Testing framework
  
  This test framework is used by the Elastic team to test Elasticsearch itself.
  Undercover, it uses the http://labs.carrotsearch.com/randomizedtesting.html[Randomized Testing] which is also used to test Apache Lucene.
  This library can be downloaded as a Maven dependency:
  
  [source,xml]
  ----
  