#1 Max memory lock doesn't change after /etc/init.d/docker restart

[Denis]

I've add command 'ulimit -l unlimited' to /etc/init.d/docker

vi /etc/init.d/docker
...

ulimit -l unlimited
start() {
...

Run command on VM (boot2docker VM)
sudo -i
/etc/init.d/docker restart
Need TLS certs for myvm1,127.0.0.1,10.0.2.15,192.168.99.100

Check ulimit:

ulimit -a

-f: file size (blocks) unlimited
-t: cpu time (seconds) unlimited
-d: data seg size (kb) unlimited
-s: stack size (kb) 8192
-c: core file size (blocks) 0
-m: resident set size (kb) unlimited
-l: locked memory (kb) 64
-p: processes 15649
-n: file descriptors 1024
-v: address space (kb) unlimited
-w: locks unlimited
-e: scheduling priority 0
-r: real-time priority 0

-l: locked memory (kb) 64 - doesn't changed

If it run manualy, all it's work:

ulimit -l unlimited

ulimit -a

-l: locked memory (kb) unlimited

Setting max memory lock need for start elasticsearch in cluster mode.