build 3448d008 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 232 | 0 skipped |
Service · infrastructure

Linux and Containers

From choosing a distribution through support agreements to automation. And the move from running Linux to running containers.

Topics capabilities · idf weight Containers containers 2.58 DevOps devops 3.86
03Solutions
02Capabilities
232Corpus

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.

Experts for this

Focus areas are not yet confirmed, so nobody is suggested here automatically. · 0 experts in corpus (n=232)

You might also like

post 0.57

Breaking and Fixing

0.7 × caps 0.6 + 0.3 × vendor 0.5 (unknown) = 0.57
post 0.48

share powershell scripts on-site

0.7 × caps 0.47 + 0.3 × vendor 0.5 (unknown) = 0.48
service 0.41

Orchestration

0.7 × caps 0.37 + 0.3 × vendor 0.5 (unknown) = 0.41