OpenShift Pod fails with runContainer: API error (500): Cannot start container [9] System error: exit status

Solution In Progress - Updated -

Issue

  • After updating docker service or kernel packages using yum update, pods fail to schedule on the node with:
1m    1m      1       {kubelet test.example.com}             Warning FailedSync      Error syncing pod, skipping: failed to "StartContainer" for "POD" with RunContainerError: "runContainer: API error (500): Cannot start container acf40056952254474054e388d99d77721e785521f02d1863bd97b780238e0e20: [9] System error: exit status 1\n"

Environment

  • Red Hat OpenShift Enterprise
    • 3.2.0
  • Kernel upgrade from kernel-3.10.0-327.22.2.el7.x86_64 to kernel-3.10.0-693.el7.x86_64
  • docker daemon version 1.10.3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.