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

pires / kubernetes-elasticsearch-cluster

Elasticsearch cluster on top of Kubernetes made easy.

Apache License 2.0

1.51k stars 690 forks source link

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

Open slavaaaaaaaaaa opened 6 years ago

slavaaaaaaaaaa commented 6 years ago

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 commented 6 years ago

Maybe a Docker problem? https://github.com/moby/moby/issues/34046

slavaaaaaaaaaa commented 6 years ago

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