kubernetes: CronJob produces seemingly random warnings for sandbox creation failures

What happened: CronJob produces seemingly random warnings relating to sandbox creation issues

What you expected to happen: No random warnings

How to reproduce it (as minimally and precisely as possible): Deploy the sample cronjob, within 10 runs on a 1-minute schedule you should see a warning about sandbox creation.

Anything else we need to know?: Does not appear to be related to memory pressure - or memory pressure is not required for it to occur, but may impact frequency. There is a corresponding issue in the docker repository here https://github.com/moby/moby/issues/40835

Environment:

  • Kubernetes version (use kubectl version): 1.16 EKS, 1.17 EKS, 1.19.2 (Docker Desktop)

  • Cloud provider or hardware configuration: AWS/EKS

  • OS (e.g: cat /etc/os-release): Amazon Linux 2

  • Errors:

Failed create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "hello-1603208700-v642l": Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:319: getting the final child's pid from pipe caused \"EOF\"": unknown

Failed create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "hello-1603207560-kd9vt": Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"read init-p: connection reset by peer\"": unknown

Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "hello-1603214100-l6pvl": Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"process_linux.go:432: running prestart hook 0 caused \\\"error running hook: exit status 1, stdout: , stderr: time=\\\\\\\"2020-10-20T17:15:06Z\\\\\\\" level=fatal msg=\\\\\\\"no such file or directory\\\\\\\"\\\\n\\\"\"": unknown

Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "hello-1603219200-5tl69": Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"\"": unknown

Failed create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "hello-1603468740-5wq58": Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"process_linux.go:438: writing syncT 'resume' caused \\\"write init-p: broken pipe\\\"\"": unknown

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 22 (15 by maintainers)

Most upvoted comments

/triage more-info

@blitzd can you confirm if #98424 fixed the issue? This landed in any 1.21.x or 1.22.x release (not eligible for backport).

@ehashman I was able to test this finally and I did not run into any warnings or errors after running the sample cronjob from the k8s docs for 24 hours.