Kubernetes can't start due to too many open files in system

I am trying create a bunch of pods, services and deployment using Kubernetes, but keep hitting the following errors when I run the kubectl describe command.

for "POD" with RunContainerError: "runContainer: API error (500): Cannot start container bbdb58770a848733bf7130b1b230d809fcec3062b2b16748c5e4a8b12cc0533a: [8] System error: too many open files in system\n"

  • Can we deploy an asp.net mvc 4 app to docker with windows container?
  • Error Installing pip Inside Docker Container
  • Cant connect to postgres docker container in docker compose
  • How to run a cron job inside a docker container?
  • Is that possible to run docker containers with devices as volumes?
  • cannot generate a service account token in kubernetes v1
  • I have already terminated all pods and try restarting the machine, but it doesn’t solve the issue. I am not an Linux expert, so I am just wondering how shall find all the open files and close them?

  • Docker - how to setup connection to container to localhost
  • Issue with docker compose
  • java.lang.IllegalStateException: Could not locate PropertySource and the fail fast property is set, failing
  • docker wordpress container can't connect to database container
  • How to get Libsodium running on Alpine Java
  • Docker Ubuntu 12.04
  • One Solution collect form web for “Kubernetes can't start due to too many open files in system”

    You can confirm which process is hogging file descriptors by running:

    lsof | awk '{print $2}' | sort | uniq -c | sort -n

    That will give you a sorted list of open FD counts with the pid of the process. Then you can look up each process w/

    ps -p <pid>

    If the main hogs are docker/kubernetes, then I would recommend following along on the issue that caesarxuchao referenced.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.