anchor.diff:  Network `none` has no communication to the outside world and is used purely for Docker containers running on the same
   box. The bind address used is usually `127.0.0.1` (loopback) here.
   
  +
  +=== Bridge network
   Network `bridge` is the default and creates a virtual interface in the container that's not available on the host. To
  -be able to communicate with other Docker containers on other hosts, the host's IP address has to be used (e.g. using
  +be able to communicate with other Docker containers on other hosts, the _host's_ IP address has to be used (e.g. using
   `external_addr=<host's address>`, or by switching to `--network=host` (see below).
   
   For instance, starting an AWS EC2 instance, `ifconfig` executed on the host shows the following interfaces:
  
positive.code: environment variable (e.g. `-e EXT-ADDR=1.2.3.4`). The container's entrypoint could then start JGroups by passing
  system property `-Dext-addr=1.2.3.4` which will set `external_addr` in TCP.
  
  
  
  ** Local
  ** Network: bridged, host
  
  == Amazon Web Services (AWS)
  ** S3 buckets for discovery
  *** external_addr (bridged network)
  ** Other discovery mechanisms
  
negative.code: TCP rather than UDP as transport. Plus, PING cannot be used and has to be replaced with different discovery protocols,
  e.g. S3_PING or GOOGLE_PING.
  
  === Bridged and host network
  
  Docker supports `none`, `bridge` and `host` networks out of the box (https://docs.docker.com/engine/userguide/networking).
  Which type of network is used is defined by the `--network` option, e.g. `--network=host`.
  