---
# source: src/content/services/en/linux-container.md
# route:  /en/services/linux-container/
title: Linux and Containers
group: infrastructure
order: 5
tags: [containers, devops]
summary: From choosing a distribution through support agreements to automation. And the move from running Linux to running containers.
photoNeed: "Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration"
stub: false
draft: false
---

## What we cover

- **Choosing a distribution** and the support agreements that go with it
- **Installation and configuration**, including the usual services such as Apache or Squid
- **Open-source and licensed software** on Linux
- **Automation**
- **DevOps**
- **Training**

## Where the decision actually gets made

At the distribution, and not for technical reasons. The day-to-day difference is the support
agreement: how long a release is maintained, how security updates are delivered, and who is
accountable when something does not work. An estate without a support agreement is cheaper,
until it is not.

## The move to containers

Anyone running Linux already holds most of the knowledge containers need. What is new is not
the operating system, it is the orchestration: how an image reaches the environment, who is
allowed to put it there, and what happens on an update.

Those questions are organisational. Which is exactly why training often gets you further
than another platform does.