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: docker stop elasticsearch-5.0
  ----
  We should still wait for Elasticsearch to be started before running tests.
  We could run Docker container using:
  
  * https://github.com/fabric8io/docker-maven-plugin[Docker Maven plugin]
  * https://plugins.jenkins.io/docker-plugin[Docker Jenkins plugin]
  
negative.code: sleep 10s
  curl "http://localhost:9200/_cluster/health?wait_for_status=yellow&timeout=30s" # <4>
  ----
  <1> Download Elasticsearch. We could also 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 main drawback of this script is that it can not run on Windows: it is not portable.
  We could rewrite it using Ant, https://github.com/elastic/elasticsearch/blob/5.0/dev-tools/smoke_test_rc.py[Python] or Groovy/Gradle:
  
  [source,xml]
  .build.xml
  