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.
jakommo
commented
2 years ago
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 https://github.com/elastic/ansible-elastic-cloud-enterprise/pull/125 and https://github.com/elastic/ansible-elastic-cloud-enterprise/issues/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 https://github.com/elastic/ansible-elastic-cloud-enterprise/pull/125 we pinned the containerd version to
1.4.3for RHEL/CentOS and back then this wascontainerd.io-1.4.3-3.1.el8.x86_64and using runc1.0.0-rc92. Today if one installs1.4.3it translates tocontainerd.io-1.4.3-3.2.el8.x86_64and that ships with runc1.0.0-rc93and is affected by https://github.com/opencontainers/runc/pull/2871 .