Try Mirantis Container Runtime

Deploy the leading enterprise container runtime with just two commands

Mirantis Container Runtime (formerly Docker Engine – Enterprise) is the secure container runtime that forms the foundation of Mirantis Container Cloud and Mirantis Kubernetes Engine. Mirantis Container Runtime provides Content Trust and FIPS 140-2 encryption, and interoperates with Mirantis Secure Registry to provide elements of a secure software supply chain.

If you use Mirantis Container Cloud to deploy Mirantis Kubernetes Engine clusters (which also provide Swarm orchestration), or use Launchpad to deploy Mirantis Kubernetes Engine, you don’t need to install Mirantis Container Runtime manually, because the automation does it for you. But there are situations where knowing how to do so is useful: for example, you may want to manually install Mirantis Container Runtime to prepare a node for adding to an existing Mirantis Kubernetes Engine cluster that isn’t being managed by Mirantis Container Cloud or Launchpad.

This tutorial shows you how to deploy Mirantis Container Runtime on a Linux node — specifically, we’re using Ubuntu 18.04 server.

If you’re looking to deploy Mirantis Container Runtime on Windows Server, check out our tutorial Getting Started with Mirantis Container Runtime on Windows Server


  • A Mac, Linux, or Windows physical or virtual machine with a desktop, used to remotely access node(s) on which Mirantis Container Runtime will be installed. Our tutorial, How to Build a Kubernetes Development Environment, shows how to set up such a machine as a VirtualBox VM.

  • One or more target machines (VMs, bare metal) running a recent version of Ubuntu Server. For purposes of this tutorial, a medium-sized VM on any desktop virtualization platform, private, or public cloud should work fine. If you’re creating, for example, a worker node specifically for use with MKE, see minimum and production hardware requirements below. Our tutorials: How to Create a Server on VirtualBox and How to Launch Virtual machines on AWS will show you how.

  • Target machines must be configured for access via SSH using keys instead of passwords, and for passwordless use of sudo for the administrative account. This is the standard for AWS EC2 VMs.

Mirantis Container Runtime can run on any hardware that supports Docker CE. As a reminder, recommended hardware requirements for configuring Mirantis Kubernetes Engine nodes are shown below.

Minimum Hardware Requirements for MKE nodes

  • 8GB of RAM for manager nodes

  • 4GB of RAM for worker nodes

  • 2 vCPUs for manager nodes

  • 25GB of free disk space.

Production Hardware Requirements for MKE nodes

  • 16GB of RAM for manager nodes

  • 4 vCPUs for manager nodes

  • 25-100GB of free disk space. SSD is recommended.

Step 1: Configure and launch your target host

Instructions for configuring your host (on AWS or VirtualBox) are the same as those provided in our Launch Virtual Machines on AWS tutorial and our How to Create a Server on VirtualBox tutorial. The former also details simple ways to set up security groups on AWS for software evaluation, and provides other details.

Step 2: Download Assets

Fill out and submit the form below to get access to the Mirantis Container Runtime installer script. Then SSH to your target VM and issue the provided command to download the script on that machine.

Download Mirantis Container Runtime installer script

Step 3: Run the script to install Mirantis Container Runtime

Next, make the script executable. On Linux, this can be done by typing:

sudo chmod +x

Then install the latest version of Mirantis Container Runtime by entering:

sudo DOCKER_URL="" ./

The script will install prerequisites automatically, plus Mirantis Container Runtime and the Docker CLI.

Step 4: (Optional) Add user to ‘docker’ group

It can be handy to add your administrative user (default ‘ubuntu’) to the ‘docker’ group, to enable use of the Docker CLI without preceding each command with sudo.

To do this, issue the following command, substituting the name of your user:

sudo usermod -aG docker $USER

Then update group settings by entering:

newgrp docker

At this point, you should be able to test whether things are working by entering:

docker run hello-world

… which runs a test container.

Next steps

At this point, you can explore Mirantis Container Runtime using the Docker CLI, or proceed to other exercises: for example, deploying a Mirantis Kubernetes Engine cluster with Launchpad.