Openshift Container Platform 3:11: /usr/bin/docker-current: Error response from daemon: containerd: container did not start before the specified timeout

Solution In Progress - Updated -

Issue

A node will mark all of its pods as terminating and get hung while the remaining pods will be stuck at "ContainerCreating" after restarting. There are no messages about the node having a bad condition, such as disk or memory pressure, but all pods will be marked as terminating and not recover. The nodes seem to go into this state during heavy traffic times.

Environment

  • Openshift Container Platform 3.11 [OCP]

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content