Merge pull request #3 from AOEpeople/oci-containers

Deprecate "Docker" and promote OCI-compatible containers
This commit is contained in:
Brian Hoffmann
2021-05-31 15:58:14 +02:00
committed by GitHub
2 changed files with 28 additions and 0 deletions

View File

@@ -0,0 +1,10 @@
---
title: "Docker"
ring: assess
quadrant: platforms-and-aoe-services
featured: false
---
Docker is best known for its capability to build and run containers. This is how we have used the term "Docker" in the Tech Radar recently. But "Docker" is also a complete production platform, where the capability to build and run Containers is only a small fraction of its capabilities. At the same time numerous alternate runtimes for containers like containerd and podman as well as image builders like Kaniko and Buildah have evolved during the last years. Thanks to the standards established by the Open Container Initiative these tools are mostly interchangeable for the purposes of building and running containers.
To be more distinct, we now recommend using [Containers and Runtimes as specified by the Open Container Initiative](/platforms-and-aoe-services/oci-container.html). "Docker" is one of many tools to achieve that.

View File

@@ -0,0 +1,18 @@
---
title: "OCI Container"
ring: adopt
quadrant: platforms-and-aoe-services
---
OCI-compatible containers are currently the most-used solution for creating and managing container-based infrastructures and deployments.
Containers and their runtime are an easy way to run applications and serivces as an isolated process (using Linux kernel cgroups, network namespaces and custom mounts).
In a DevOps environment, this helps a lot as we can run the exact same software and runtime (such as NodeJS) on both production and locally while developing. This enables us to debug our software much easier. We can compose our project development setup out of small containers. Also, containers allow us to keep our development environment much simpler and independent of our developer's operating system or pre-installed software versions.
In a CI environment building the containers allows us to package and test the whole environment instead of different software components on different runtimes in a much more stable way.
Backed by services such as [Kubernetes](/platforms-and-aoe-services/kubernetes.html) and [Helm](/platforms-and-aoe-services/helm.html), we can deploy containers on a flexible infrastructure and enable our developers to test their software more easily in different environments.
Here at AOE, we use containers in different projects to become more flexible and faster, which increases our focus on development of even better and more stable software.