You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TL;DR: We should update the containerd version in RHEL/CentOS (i.e. here) to 1.5.* to fix runc the issue described bwelow and also match our own install docs, that use sudo yum install -y docker-ce-20.10* docker-ce-cli-20.10* containerd.io-1.5.* today (ECE 3.4).
We worked with a user yesterday that had issues with ECE (or better docker), where newly created containers would be stuck in "Created" state, similar to the issue above.
In #125 we pinned the containerd version to 1.4.3 for RHEL/CentOS and back then this was containerd.io-1.4.3-3.1.el8.x86_64 and using runc 1.0.0-rc92.
Today if one installs 1.4.3 it translates to containerd.io-1.4.3-3.2.el8.x86_64 and that ships with runc 1.0.0-rc93 and is affected by opencontainers/runc#2871 .
The text was updated successfully, but these errors were encountered:
TL;DR: We should update the containerd version in RHEL/CentOS (i.e. here) to
1.5.*
to fix runc the issue described bwelow and also match our own install docs, that usesudo yum install -y docker-ce-20.10* docker-ce-cli-20.10* containerd.io-1.5.*
today (ECE 3.4).This is a follow up to #125 and #121.
We worked with a user yesterday that had issues with ECE (or better docker), where newly created containers would be stuck in "Created" state, similar to the issue above.
In #125 we pinned the containerd version to
1.4.3
for RHEL/CentOS and back then this wascontainerd.io-1.4.3-3.1.el8.x86_64
and using runc1.0.0-rc92
.Today if one installs
1.4.3
it translates tocontainerd.io-1.4.3-3.2.el8.x86_64
and that ships with runc1.0.0-rc93
and is affected by opencontainers/runc#2871 .The text was updated successfully, but these errors were encountered: