The following is an overview of the different installation methods available. All of these methods equally result in a system configured to run Kata Containers.
Kata Containers requires nested virtualization or bare metal. See the hardware requirements to see if your system is capable of running Kata Containers.
Notes:
- Packaged installation methods uses your distribution's native package format (such as RPM or DEB).
- You are strongly encouraged to choose an installation method that provides automatic updates, to ensure you benefit from security updates and bug fixes.
| Installation method | Description | Automatic updates | Use case |
|---|---|---|---|
| Using official distro packages | Kata packages provided by Linux distributions official repositories | yes | Recommended for most users. |
| Using snap | Easy to install | yes | Good alternative to official distro packages. |
| Automatic | Run a single command to install a full system | No! | For those wanting the latest release quickly. |
| Manual | Follow a guide step-by-step to install a working system | No! | For those who want the latest release with more control. |
| Build from source | Build the software components manually | No! | Power users and developers only. |
Kata packages are provided by official distribution repositories for:
| Distribution (link to installation guide) | Minimum versions |
|---|---|
| CentOS | 8 |
| Fedora | 34 |
Note:
All users are encouraged to uses the official distribution versions of Kata Containers unless they understand the implications of alternative methods.
Note: The snap installation is available for all distributions which support
snapd.
Use snap to install Kata Containers from https://snapcraft.io.
Use kata-manager to automatically install a working Kata Containers system.
Follow the containerd installation guide.
Note:
Power users who decide to build from sources should be aware of the implications of using an unpackaged system which will not be automatically updated as new releases are made available.
Building from sources allows power users who are comfortable building software from source to use the latest component versions. This is not recommended for normal users.
- Amazon Web Services (AWS)
- Google Compute Engine (GCE)
- Microsoft Azure
- Minikube
- VEXXHOST OpenStack Cloud
- The upgrading document.
- The developer guide.
- The runtime documentation.