Solution to ES memory overflow when starting docker

-Xms5g
-Xmx5g

## JVM configuration
################################################################
## IMPORTANT: JVM heap size
################################################################
##
## You should always set the min and max JVM heap
## size to the same value. For example, to set
## the heap to 4 GB, set:
##
## -Xms4g
## -Xmx4g
##
## See https://www.elastic.co/guide/en/elasticsearch/reference/current/heap-size.html
## for more information
##
################################################################
# Xms represents the initial size of total heap space
# Xmx represents the maximum size of total heap space
-Xms5g
-Xmx5g
################################################################
## Expert settings
################################################################
##
## All settings below this section are considered
## expert settings. Don't tamper with them unless
## You understand what you are doing
##
################################################################
## GC configuration
-XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=75
-XX:+UseCMSInitiatingOccupancyOnly
## optimizations
# pre-touch memory pages used by the JVM during initialization
-XX:+AlwaysPreTouch
## basic
# force the server VM (remove on 32-bit client JVMs)
-server
# explicitly set the stack size (reduce to 320k on 32-bit client JVMs)
-Xss1m
# set to headless, just in case
-Djava.awt.headless=true
# ensure UTF-8 encoding by default (eg filenames)
-Dfile.encoding=UTF-8
# use our provided JNA always versus the system one
-Djna.nosys=true
# use old-style file permissions on JDK9
-Djdk.io.permissionsUseCanonicalPath=true
# flags to configure Netty
-Dio.netty.noUnsafe=true
-Dio.netty.noKeySetOptimization=true
-Dio.netty.recycler.maxCapacityPerThread=0
# log4j 2
-Dlog4j.shutdownHookEnabled=false
-Dlog4j2.disable.jmx=true
-Dlog4j.skipJansi=true
## heap dumps
# generate a heap dump when an allocation from the Java heap fails
# heap dumps are created in the working directory of the JVM
-XX:+HeapDumpOnOutOfMemoryError
# specify an alternative path for heap dumps
# ensure the directory exists and has sufficient space
#-XX:HeapDumpPath=${heap.dump.path}
## GC logging
#-XX:+PrintGCDetails
#-XX:+PrintGCTimeStamps
#-XX:+PrintGCDateStamps
#-XX:+PrintClassHistogram
#-XX:+PrintTenuringDistribution
#-XX:+PrintGCApplicationStoppedTime
# log GC status to a file with time stamps
# ensure the directory exists
#-Xloggc:${loggc}
# By default, the GC log file will not rotate.
# By uncommenting the lines below, the GC log file
# will be rotated every 128MB at most 32 times.
#-XX:+UseGCLogFileRotation
#-XX:NumberOfGCLogFiles=32
#-XX:GCLogFileSize=128M
# Elasticsearch 5.0.0 will throw an exception on unquoted field names in JSON.
# If documents were already indexed with unquoted fields in a previous version
# of Elasticsearch, some operations may throw errors.
#
# WARNING: This option will be removed in Elasticsearch 6.0.0 and is provided
# only for migration purposes.
#-Delasticsearch.json.allow_unquoted_field_names=true

docker run -d -i -t -m 256M --memory-swap 512M --name centos2.12 centos /bin/bash

-m, --memory 
# Memory limit size, the unit can be b, k, M, g; the minimum is 4M
--memory-swap
#Total limit of memory + swap partition size --memory-reservation #Reserved memory size; minimum memory occupied by the container on the host;
--oom-kill-disable
# out-of-memory memory overflow; limit the killing of container processes, not set by default --oom-score-adj
# The priority of the container being killed by the OOM killer, the range is [-1000, 1000], the default is 0
--memory-swappiness
# Used to set the virtual memory control behavior of the container. The value is an integer between 0 and 100 --kernel-memory
Core memory limit, minimum is 4M.

--memory-swap is not the swap partition, but the size of memory + swap;
The container's swap partition swap = memory-swap - memory

memory-swap is not set or is set to 0;
The swap size of the container is the size of the memory.
Maximum memory used by the container's process = memory + swap

When memory-swap is set to -1;
The container memory size is the size set by memory;
The swap partition size is the host machine swap size;
The maximum memory that the container process can use = memory + host swap size;

--oom-kill-disable
Limit the kill container process; (Must be set after memory to be limited;)
docker run -d -i -t -m 256M --oom-kill-disable --name Centos-1 centos /bin/bash

Core memory includes:
stack pages
slab pages
socket memory pressure
TCP memory pressure

docker run -d -i -t -m 500M --kernel-memory 128M --name Centos-2 centos /bin/bash
Limit container memory to 256M; limit core memory to 128M.
docker run -d -i -t --kernel-memory 128M --name Centos-3 centos /bin/bash
The memory is the host memory size, and the core memory is limited to 128M

--memory-swappiness is used to set this ratio.
--memory-swappiness can be set from 0 to 100.
# 0 means turning off anonymous page swapping.
# 100 means all anonymous pages can be exchanged. By default, if --memory-swappiness is not applied, the value is inherited from the parent process.
docker run -d -i -t --memory-swappiness=0 --name Centos-4 centos /bin/bash
Setting --memory-swappiness to 0 preserves the container's working set and avoids the performance penalty of the swap agent.

sysctl vm.swappiness = 100 
# cat /proc/sys/vm/swappiness