Kubernetes and ulimit

Hi,

I’m using Kubernetes 1.14.7 on AWS (EKS).

I’ve noticed that if I use “ulimit -a” inside a running Docker container, the values returned are different than the ones I get when I use “ulimit -a” inside a running Kubernetes container - even though they are created from the same Docker image.

Is this something I should be worried about? The Kubernetes “ulimit -a” returns smaller values… Are they enforced?

“ulimit -a” response when issued inside my Docker container:

core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 30952
max locked memory (kbytes, -l) 16384
max memory size (kbytes, -m) unlimited
open files (-n) 1048576
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

“ulimit -a” response when issued inside my Kubernetes container:

core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 127057
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 65536
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

Thank you kindly :slight_smile: