Master pods refuse to start with memory limits set on AWS EKS

[slavaaaaaaaaaa]

Whenever I try running master pods with memory limits, I get this error:

Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"read init-p: connection reset by peer\""

This oddly doesn't happen for es-data pods. I'm using slightly modified statefulset versions of both.

[pires]

Maybe a Docker problem? moby/moby#34046

[slavaaaaaaaaaa]

@pires I should've mentioned I'm running in EKS.