The Mirantis Container Runtime (MCR 29.0) for Red Hat Enterprise Linux 9 AMI image provides users quick and secure way to deploy and run business critical applications with enterprise support
If your teams are already building and managing applications with Docker, you can promote those workloads to production without needing to retool or migrate. Mirantis Container Runtime (formerly Docker Engine - Enterprise) is fully compatible with Docker-based workflows and toolchains, providing a seamless path from development to production. Developers can continue using the same CLI, Dockerfiles, and APIs they already know, while IT can seamlessly promote those workloads into production with the assurance of an Enterprise Support agreement with guaranteed SLAs.
MCR, built on CNCF Docker Moby, is purpose-built for running containers at scale in production. It offers tested and validated releases across a broad set of operating systems, with robust CVE patching and bug fixes to ensure workload stability. MCR also enables hybrid and distributed cloud strategies by supporting the broadest range of platforms in the industry while meeting strict compliance standards.
Mirantis acquired Docker Enterprise in 2019, and since then has been contributing upstream to Docker Moby and related technologies. Today, MCR provides enterprise-ready container infrastructure that aligns with open standards, enabling customers to run Docker-based applications reliably in mission-critical environments.
The latest MCR 29 plan introduces a number of important platform enhancements designed to improve operability, developer experience, and production readiness. These include improved IPv6 networking support, device code login support for Docker Hub, the containerd image store as the default backend for new installations, enhanced IP address management visibility, additional Docker Swarm service options, and API and SDK improvements for third-party integrations.
Key Features include:
Security: AppArmor application-level access control, SELinux mandatory access control (MAC), FIPS 140-2 validated encryption, image signature verification, and support for sandboxed and isolated container runtimes such as Kata and gVisor
Performance: Optimized architecture with minimal resource overhead, fast container startup for efficient deployment and scaling
Ease of Use: Intuitive Docker CLI and support for Docker Swarm container orchestration in addition to Kubernetes
Multi-Cloud Interoperability: Support for multiple cloud platforms and operating systems, giving customers seamless portability with consistent management
AI Workload Support: Native AI container support, enhanced GPU Support with Container Device Interface (CDI) to integrate different accelerators and device types
Modern Platform Enhancements in MCR 29: Improved IPv6 stability, modernized image management with containerd image store, enhanced network IPAM visibility, new Swarm service controls, and API/SDK updates for developers
As an OCI-certified and CRI-conformant runtime, Mirantis Container Runtime (MCR) aligns with industry standards and is compatible with leading container orchestration platforms. Tested at scale and proven with hundreds of customer deployments, Mirantis Container Runtime is used to support mission-critical applications from data centers to the edge.
This offering currently includes Basic 8x5 Support, offering business-hour assistance via web and email, access to a robust knowledge base, regular maintenance updates, critical issue resolutions, and security and product bulletins. This support tier provides reliable remote incident resolution to help ensure your container environments remain secure and up to date during standard operating hours.
For organizations requiring broader coverage or fully managed services, Mirantis offers OpsCare and OpsCare Plus support upgrades. OpsCare provides enterprise-grade 24/7 support, lifecycle guidance, and escalation management. OpsCare Plus extends this with up to 99.99% SLA, a designated Customer Success Manager (CSM), a full ITIL service management suite, and customer advocacy. To explore these enhanced support options and identify the right fit for your workloads, please contact Mirantis sales.
Learn more ()
Highlights
MCR provides FIPS 140-2 Validated cryptography ensuring that you meet the highest standards necessary to comply with the federal requirements.
MCR is certified to run on multiple operating systems and infrastructures, for consistent runtime regardless of the platform.
MCR provides enterprise support, with regular CVE and security updates
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
You pay by the hour for the container runtime, billed per Amazon EC2 instance you run it on. Each dimension maps to a specific EC2 instance type, all sized at xlarge. The list spans many instance families, including general purpose, compute, memory, storage, and GPU-accelerated types. Pricing follows the instance you select, so your cost tracks how many instances run and for how long. There are no tiers or upfront commitments here; charges accrue only while instances run. The runtime capabilities stay the same across every instance type, so your choice reflects hardware needs, not feature differences.
Top-of-mind questions for buyers
What does the hourly charge cover for each xlarge instance type?
Each dimension bills the container runtime software per hour on one running xlarge Amazon EC2 instance of that type. One unit equals one instance running for one hour. The rate is tied to the specific instance family you launch, and separate AWS charges for the instance itself apply on top.
Am I charged when an instance running the runtime is stopped or powered off?
Software charges meter running time only. A fully stopped or powered-off instance stops accruing the hourly runtime charge. Underlying AWS storage costs for the instance may still apply while it is stopped, but the runtime license bills only for hours the instance actually runs.
If I switch from one xlarge instance type to another, how does my bill change?
Your cost follows whichever instance type you run. Moving to a different xlarge type applies that type's hourly rate for the hours it runs. The runtime capabilities do not change, so the difference reflects hardware choice, not features. Charges from each instance accrue independently and appear on the same invoice.
www.mirantis.com
Helpful?
Vendor refund policy
none
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
In the AWS Management Console, go to the Services menu.
Under the Compute section, select EC2.
In the left-hand navigation pane, select AMI Catalog
Search for the Linux image you want to launch. i.e. Mirantis Container Runtime for Ubuntu
Click on the Launch Instance button.
Step 3: Search for the Desired AMI
In the Choose an Amazon Machine Image (AMI) step, select the AWS Marketplace tab.
Use the search bar to find the desired AMI. For example, you can search for "Ubuntu 20.04" or any other specific AMI you need.
Browse through the search results and select the AMI that matches your requirements.
Step 4: Subscribe to the AMI
Click on the Select button next to the desired AMI.
Review the pricing details and terms of use.
Click on the Continue button to subscribe to the AMI.
Step 5: Configure Instance Details
In the Choose an Instance Type step, select the instance type that meets your requirements (e.g., t2.micro, m5.large).
Click on the Next: Configure Instance Details button.
Configure the instance details, such as the number of instances, network settings, and IAM role.
Click on the Next: Add Storage button.
Step 6: Add Storage
Configure the storage settings for your instance. You can add additional EBS volumes if needed.
Click on the Next: Add Tags button.
Step 7: Add Tags
Add any tags to your instance to help you identify and manage it.
Click on the Next: Configure Security Group button.
Step 8: Configure Security Group
Configure the security group to allow the necessary inbound traffic. For example, you might need to allow SSH (port 22) for Linux instances or RDP (port 3389) for Windows instances.
Click on the Review and Launch button.
Step 9: Review and Launch
Review all the configuration details for your instance.
Click on the Launch button.
In the Select an existing key pair or create a new key pair dialog, choose an existing key pair or create a new one to access your instance.
Acknowledge that you have access to the selected key pair and click on the Launch Instances button.
Step 10: Access Your Instance
After the instance is launched, go to the Instances section in the EC2 dashboard.
Select your instance and click on the Connect button to get the connection details.
Use the provided instructions to connect to your instance via SSH for Linux.
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
The Mirantis Container Runtime (MCR 25.0) for Red Hat Enterprise Linux 9 AMI image provides users quick and secure way to deploy and run business critical applications with enterprise support
The Mirantis Container Runtime (MCR 23.0) for Red Hat Enterprise Linux 8 AMI image provides users quick and secure way to deploy and run business critical applications with enterprise support
The Mirantis Container Runtime (MCR 25.0) for Ubuntu 24.04 AMI image provides users quick and secure way to deploy and run business critical applications with enterprise support
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.