Webinar: Why on-prem should be an important a part of your cloud native strategy   |   Register Now

Webinar: Why on-prem should be an important a part of your cloud native strategy


Mirantis Container Runtime

Industry Leading Container Runtime

Mirantis Container Runtime enables containers to run efficiently on any substrate, powering business critical applications at the world’s leading companies.

+  Intrinsic security+  Windows & Linux support+  Proven at scale

Running Containers Efficiently, Everywhere

Container runtimes activate and manage the components required to run containers. Mirantis Container Runtime is the industry-leading, high-level runtime at the heart of Mirantis Kubernetes Engine, enabling it to operate Swarm and Kubernetes containers efficiently on any substrate. It is based on containerd, the Cloud Native Computing Foundation (CNCF) core container runtime.

Preferred for Kubernetes

Mirantis Container Runtime is the most popular container runtime for Kubernetes and Swarm, and is validated to work with Kubernetes Container Runtime Interface (CRI).

Runs Anywhere

It ensures Mirantis Kubernetes Engine worker nodes operate efficiently on any substrate. Portable DevOps: operators can use familiar tools and consistent automation, everywhere.

Secure Supply Chain

The most efficient and secure solution for highly regulated industries, our runtime can be integrated with Mirantis Secure Registry and Mirantis Kubernetes Engine, and has the ability to run vulnerability scans on Docker containers.

Get 8x5 Support for Linux or Windows Server

Purchase a 1-year subscription with 8x5 business hours support for Mirantis Container Runtime (formerly Docker Engine - Enterprise) for compatible Linux or Windows Server (minimum 5 Nodes required for online purchase, maximum to not exceed 19 nodes).

Starting at $900.00 per node

Key Features & Capabilities

Intrinsic Security

Mirantis Container Runtime is secure by default, deploying with restricted host access, end-to-end encryption, secure mutual TLS authentication, and cryptographic node identity. Security features are supported by Mirantis Kubernetes Engine’s FIPS 140-2-compliant cryptographic module, validated by the National Institute of Science and Technology (NIST), and fulfilling key requirements of the Federal Information Security Management Act (FISMA). Learn more about about the Mirantis Container Registry FIPS 140-2 certification in our blog.

Multiple Operating Systems and Infrastructures

Mirantis Container Runtime is certified to run on multiple operating systems including CentOS, RHEL, Ubuntu, and Windows for consistent runtime regardless of the platform — and orchestrate nodes in Kubernetes, Swarm, or ‘mixed’ configurations.

Certified Plugins

Plugin support lets Mirantis Kubernetes Engine exploit best-in-class Kubernetes container networking fabrics like Calico, Kubernetes ingress solutions such as Istio, and GPU-equipped and other specialized hardware. Component and node capabilities discovered by the plugin are labeled in Mirantis Kubernetes Engine, appropriately tagged, and made immediately available to application deployments for scheduling.

Enforce Signed Images

Our Kubernetes container runtime lets you validate container provenance by requiring proper digital signing of images before they can be deployed. Users are prevented from using container images or composing containers using base layers from unknown sources.

Get started with Mirantis Container Runtime

Mirantis Container Runtime is the secure container runtime that forms the foundation of Mirantis Container Cloud and Mirantis Kubernetes Engine. Deploy with just two commands.

Get Started Read The Docs


What are the supported operating systems that I can host my containers using Mirantis Container Runtime?

How do I know my containers are secure when using Mirantis Container Runtime?

How do I extend the functionality of my containers when using Mirantis Container Runtime?

Are my containers verified against the latest known vulnerabilities?

What more is provided with Mirantis Container Runtime over the upstream Docker runtime?