DE · EN
Call us
+41 44 508 80 00 Ueberlandstrasse 1, 8600 Dübendorf
build 7bbbddf7 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 267 | ● 0 skipped | | format
apiVersion: soultec.ch/v1kind: Servicemetadata: name: linux-container locale: en labels: group: infrastructure capability/containers: 2.39 capability/devops: 3.42 annotations: source: src/content/services/en/linux-container.md route: /en/services/linux-container/ schema: /nerd/schema/services.json markdown: /en/services/linux-container.mdspec: 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 sections: - heading:

What we cover

 body: | - **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** - heading:

Where the decision actually gets made

 body: | 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. - heading:

The move to containers

 body: | 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.status: corpus: 267 solutions: - {ref: solutions/morpheus, score: 0.40} - {ref: solutions/vmware/vmware-cloud-foundation/vks, score: 0.38} - {ref: solutions/vmware/vmware-cloud-foundation/vsphere-mit-tanzu, score: 0.38} - {ref: solutions/vmware/vmware-cloud-foundation/addon/application-services, score: 0.37} alsoLike: - {ref: experts/louis-kern, score: 0.60} - {ref: experts/tobias-waelti, score: 0.60} - {ref: posts/breaking-and-fixing-gitlab, score: 0.56} experts: - {ref: experts/louis-kern, score: 0.60} - {ref: experts/tobias-waelti, score: 0.60} - {ref: experts/christian-schnyder, score: 0.33}
{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "linux-container", "locale": "en", "labels": { "group": "infrastructure", "capability/containers": "2.39", "capability/devops": "3.42" }, "annotations": { "source": "src/content/services/en/linux-container.md", "route": "/en/services/linux-container/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/linux-container.md" } }, "spec": { "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 }, "sections": [ { "heading": "

What we cover

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

Where the decision actually gets made

", "body": "At the distribution, and not for technical reasons. The day-to-day difference is the support\nagreement: how long a release is maintained, how security updates are delivered, and who is\naccountable when something does not work. An estate without a support agreement is cheaper,\nuntil it is not." }, { "heading": "

The move to containers

", "body": "Anyone running Linux already holds most of the knowledge containers need. What is new is not\nthe operating system, it is the orchestration: how an image reaches the environment, who is\nallowed to put it there, and what happens on an update.\n\nThose questions are organisational. Which is exactly why training often gets you further\nthan another platform does." } ], "status": { "corpus": 267, "solutions": [ { "ref": "solutions/morpheus", "score": "0.40" }, { "ref": "solutions/vmware/vmware-cloud-foundation/vks", "score": "0.38" }, { "ref": "solutions/vmware/vmware-cloud-foundation/vsphere-mit-tanzu", "score": "0.38" }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/application-services", "score": "0.37" } ], "alsoLike": [ { "ref": "experts/louis-kern", "score": "0.60" }, { "ref": "experts/tobias-waelti", "score": "0.60" }, { "ref": "posts/breaking-and-fixing-gitlab", "score": "0.56" } ], "experts": [ { "ref": "experts/louis-kern", "score": "0.60" }, { "ref": "experts/tobias-waelti", "score": "0.60" }, { "ref": "experts/christian-schnyder", "score": "0.33" } ] }}
apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "linux-container"locale = "en"[metadata.labels]group = "infrastructure""capability/containers" = "2.39""capability/devops" = "3.42"[metadata.annotations]source = "src/content/services/en/linux-container.md"route = "/en/services/linux-container/"schema = "/nerd/schema/services.json"markdown = "/en/services/linux-container.md"[spec]title = "Linux and Containers"group = "infrastructure"order = 5tags = ["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 = falsedraft = false[[sections]]heading = "

What we cover

"body = '''- **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**'''[[sections]]heading = "

Where the decision actually gets made

"body = '''At the distribution, and not for technical reasons. The day-to-day difference is the supportagreement: how long a release is maintained, how security updates are delivered, and who isaccountable when something does not work. An estate without a support agreement is cheaper,until it is not.'''[[sections]]heading = "

The move to containers

"body = '''Anyone running Linux already holds most of the knowledge containers need. What is new is notthe operating system, it is the orchestration: how an image reaches the environment, who isallowed to put it there, and what happens on an update.Those questions are organisational. Which is exactly why training often gets you furtherthan another platform does.'''[status]corpus = 267[[status.solutions]]ref = "solutions/morpheus"score = "0.40"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/vks"score = "0.38"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/vsphere-mit-tanzu"score = "0.38"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/addon/application-services"score = "0.37"[[status.alsoLike]]ref = "experts/louis-kern"score = "0.60"[[status.alsoLike]]ref = "experts/tobias-waelti"score = "0.60"[[status.alsoLike]]ref = "posts/breaking-and-fixing-gitlab"score = "0.56"[[status.experts]]ref = "experts/louis-kern"score = "0.60"[[status.experts]]ref = "experts/tobias-waelti"score = "0.60"[[status.experts]]ref = "experts/christian-schnyder"score = "0.33"
<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>linux-container</name> <locale>en</locale> <labels> <group>infrastructure</group> <entry key="capability/containers">2.39</entry> <entry key="capability/devops">3.42</entry> </labels> <annotations> <source>src/content/services/en/linux-container.md</source> <route>/en/services/linux-container/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/linux-container.md</markdown> </annotations> </metadata> <spec> <title>Linux and Containers</title> <group>infrastructure</group> <order>5</order> <tags> <item>containers</item> <item>devops</item> </tags> <summary>From choosing a distribution through support agreements to automation. And the move from running Linux to running containers.</summary> <photoNeed>Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration</photoNeed> <stub>false</stub> <draft>false</draft> </spec> <sections> <section> <heading>

What we cover

</heading> <body>- **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** </body> </section> <section> <heading>

Where the decision actually gets made

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

The move to containers

</heading> <body>Anyone running Linux already holds most of the knowledge containers need. What is new is notthe operating system, it is the orchestration: how an image reaches the environment, who isallowed to put it there, and what happens on an update.Those questions are organisational. Which is exactly why training often gets you furtherthan another platform does. </body> </section> </sections> <status> <corpus>267</corpus> <solutions> <item> <ref>solutions/morpheus</ref> <score>0.40</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/vks</ref> <score>0.38</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/vsphere-mit-tanzu</ref> <score>0.38</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/addon/application-services</ref> <score>0.37</score> </item> </solutions> <alsoLike> <item> <ref>experts/louis-kern</ref> <score>0.60</score> </item> <item> <ref>experts/tobias-waelti</ref> <score>0.60</score> </item> <item> <ref>posts/breaking-and-fixing-gitlab</ref> <score>0.56</score> </item> </alsoLike> <experts> <item> <ref>experts/louis-kern</ref> <score>0.60</score> </item> <item> <ref>experts/tobias-waelti</ref> <score>0.60</score> </item> <item> <ref>experts/christian-schnyder</ref> <score>0.33</score> </item> </experts> </status></manifest>
Service · infrastructure

Linux and Containers

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

Topics Containers 2.39 DevOps 3.42
04Solutions
02Capabilities
267Corpus

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

Louis Kern

Senior System Engineer

DevOpsContainers
0.60

Tobias Wälti

Senior System Engineer

DevOpsContainers
0.60

Christian Schnyder

Senior System Engineer

DevOps
0.33
Maybe you? Take a look at our open roles.

You might also like

expert 0.60

Louis Kern

expert 0.60

Tobias Wälti

post 0.56

Breaking and Fixing