MCR 20.10 Compatibility Matrix¶
Mirantis Container Runtime (MCR) enables containers to run efficiently on any substrate, powering business critical applications at the world’s leading companies.
Mirantis validates MCR for the operating system environments specified here, adhering to the MKE, MSR, and MCR Maintenance Lifecycle. Support for MCR is defined in the Mirantis Cloud Native Platform Subscription Services agreement.
Note
MKE 3.5.x and 3.4.x do not support Windows Server 2022.
OS distributed versions not listed in the following matrix are not supported under Standard Support Subscriptions. For such versions, contact your Mirantis rep to discuss support options.
Caution
CentOS 8 entered EOL status as of 31-December-2021. For this reason, Mirantis no longer supports CentOS 8 for all versions of MCR. We encourage customers who are using CentOS 8 to migrate onto any one of the supported operating systems, as further bug fixes will not be forthcoming.
MCR |
Max. supported Client API |
Platform |
Versions |
|---|---|---|---|
20.10.13 |
1.41 |
CentOS |
7.9.2009, 7.8.2003 |
Oracle Linux |
7.9, 7.8 |
||
RHEL |
8.6, 8.5, 8.4, 7.9, 7.8 |
||
Rocky Linux |
8.6, 8.5 |
||
SLES |
15 SP3, 12 SP5 |
||
Ubuntu |
20.04.41, 20.04.3, 20.04.2, 20.04.1, 20.04, 18.04.6, 18.04.5, 18.04.4, 18.04.3, 18.04.2, 18.04.1, 18.04 |
||
Microsoft Windows Enterprise Server |
2022, 2019 |
||
20.10.12 |
1.41 |
CentOS |
7.9.2009, 7.8.2003 |
Oracle Linux |
7.9, 7.8 |
||
RHEL |
8.6, 8.5, 8.4, 7.9, 7.8 |
||
Rocky Linux |
8.6, 8.5 |
||
SLES |
15 SP3, 12 SP5 |
||
Ubuntu |
20.04.41, 20.04.3, 20.04.2, 20.04.1, 20.04, 18.04.6, 18.04.5, 18.04.4, 18.04.3, 18.04.2, 18.04.1, 18.04 |
||
Microsoft Windows Enterprise Server |
2019 |
||
20.10.11 |
1.41 |
CentOS |
7.9.2009, 7.8.2003 |
Oracle Linux |
7.9, 7.8 |
||
RHEL |
8.4, 8.2, 7.9, 7.8 |
||
Rocky Linux |
8.5 |
||
SLES |
15 SP3, 12 SP5 |
||
Ubuntu |
20.04.41, 20.04.3, 20.04.2, 20.04.1, 20.04, 18.04.6, 18.04.5, 18.04.4, 18.04.3, 18.04.2, 18.04.1, 18.04 |
||
Microsoft Windows Enterprise Server |
2019 |
||
20.10.10 |
1.41 |
CentOS |
7.9.2009, 7.8.2003 |
Oracle Linux |
7.9, 7.8 |
||
RHEL |
8.4, 8.2, 7.9, 7.8 |
||
SLES |
15 SP3, 12 SP5 |
||
Ubuntu |
20.04.3, 18.04.6 |
||
Microsoft Windows Enterprise Server |
2019 |
||
20.10.9 |
1.41 |
CentOS |
7.9.2009, 7.8.2003 |
Oracle Linux |
7.9, 7.8 |
||
RHEL |
8.4, 8.2, 8.1, 7.9, 7.8 |
||
SLES |
15 SP3, 15 SP2, 12 SP5 |
||
Ubuntu |
20.04.3, 18.04.6 |
||
Microsoft Windows Enterprise Server |
2019 |
||
20.10.8 |
1.41 |
CentOS |
7.9.2009, 7.8.2003 |
Oracle Linux |
7.9, 7.8 |
||
RHEL |
8.4, 8.2, 8.1, 7.9, 7.8 |
||
SLES |
15 SP3, 15 SP2, 12 SP5 |
||
Ubuntu |
20.04.3, 18.04.6 |
||
Microsoft Windows Enterprise Server |
2019 |
||
20.10.7 |
1.41 |
CentOS |
7.9.2009, 7.8.2003 |
Oracle Linux |
7.9, 7.8 |
||
RHEL |
8.4, 8.2, 8.1, 7.9, 7.8 |
||
SLES |
15 SP3, 15 SP2, 12 SP5 |
||
Ubuntu |
20.04.3, 18.04.6 |
||
Microsoft Windows Enterprise Server |
2019 |
||
20.10.6 |
1.41 |
CentOS |
7.9.2009, 7.8.2003 |
Oracle Linux |
7.9, 7.8 |
||
RHEL |
8.4, 8.2, 8.1, 7.9, 7.8 |
||
SLES |
15 SP3, 15 SP2, 12 SP5 |
||
Ubuntu |
20.04.3, 18.04.6 |
||
Microsoft Windows Enterprise Server |
2019 |
||
20.10.5 |
1.41 |
CentOS |
7.9.2009, 7.8.2003 |
Oracle Linux |
7.9, 7.8 |
||
RHEL |
8.3, 8.2, 8.1, 7.9, 7.8 |
||
SLES |
15 SP3, 15 SP2, 12 SP5 |
||
Ubuntu |
20.04.2, 18.04.4 |
||
Microsoft Windows Enterprise Server |
2019 |
||
20.10.4 |
1.41 |
CentOS |
7.9.2009, 7.8.2003 |
Oracle Linux |
7.9, 7.8 |
||
RHEL |
8.3, 8.2, 8.1, 7.9, 7.8 |
||
SLES |
15 SP3, 15 SP2, 12 SP5 |
||
Ubuntu |
20.04.2, 18.04.4 |
||
Microsoft Windows Enterprise Server |
2019 |
||
20.10.0 |
1.41 |
CentOS |
7.9.2009, 7.8.2003 |
Oracle Linux |
7.9 7.8 |
||
RHEL |
8.3, 8.2, 8.1, 7.9, 7.8 |
||
SLES |
15 SP3, 15 SP2, 12 SP5 |
||
Ubuntu |
20.04.2, 18.04.4 |
||
Microsoft Windows Enterprise Server |
2019 |
1 A known critical issue is present in the 5.13.0-1028-aws and
5.13.0-1029-aws kernels of the Ubuntu AMIs on AWS. The issue was
resolved in the 5.13.0-1030-aws kernel. If you are an AWS user, refer to
Docker container creation causes kernel oops on linux-aws
5.13.0.1028.31~20.04.22 and
Docker container ports cannot be allocated,
otherwise check with your cloud provider.