Docker container running Tomcat encounters the pit

Using the Docker container to run Tomcat, because the same host ran a number of containers, plus the host itself ran a lot of processes, resulting in the total number of processes 8000+, and the container in Tomcat's startup script will call the setenv.sh, There is such a sentence in setenv.sh ulimit-u 8192, because the number of system processes has reached 8192, so when you start Tomcat error:

Tomcat/bin/catalina.sh:fork:retry:no Child Processes
Tomcat/bin/catalina.sh:fork:retry:no Child Processes
Tomcat/bin/catalina.sh:fork:retry:no Child Processes
Tomcat/bin/catalina.sh:fork:retry:no Child Processes
Tomcat/bin/catalina.sh:fork:resource temporarily unavailable

Tomcat could not start, later modified setenv.sh, Ulimit-u 8192, changed to Ulimit-u 58192, Tomcat can start normally.

The System max proc configuration (ulimit-a view) is in/etc/security/limits.conf.

System Limit setting modification method recommended Link:

http://pvbutler.blog.51cto.com/7662323/1558092

Http://jingyan.baidu.com/article/1974b289a397d1f4b1f77495.html

Http://www.cnblogs.com/mylingc/archive/2013/05/24/3097416.html

Docker container running Tomcat encounters the pit