DE · EN
Call us
+41 44 508 80 00 Ueberlandstrasse 1, 8600 Dübendorf
build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | format run

$ soultec get service/linux-container -o yaml$ soultec get service/linux-container -o json$ soultec get service/linux-container -o toml$ soultec get service/linux-container -o xml$ python3 linux-container.pyPS> ./linux-container.ps1$ go run linux-container.go$ node linux-container.js

apiVersion: soultec.ch/v1kind: Servicemetadata: name: linux-container locale: en labels: group: infrastructure capability/containers: 2.51 capability/devops: 3.16 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 audience: [enterprise, provider] 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 - **Patch and update service** - **Operational support** while it runs - **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: 315 solutions: - {ref: solutions/vmware/vmware-cloud-foundation/vks, score: 0.40} - {ref: solutions/hpe/hpe-morpheus, score: 0.39} - {ref: solutions/igel/igel-managed-containers, score: 0.39} - {ref: solutions/vmware/vmware-cloud-foundation/addon/application-services, score: 0.38} alsoLike: - {ref: experts/louis-kern, score: 0.60} - {ref: posts/breaking-and-fixing-gitlab, score: 0.54} - {ref: experts/tobias-waelti, score: 0.52} experts: - {ref: experts/louis-kern, score: 0.60} - {ref: experts/tobias-waelti, score: 0.52} - {ref: experts/marco-mattei, score: 0.35} search: /en/search.json
{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "linux-container", "locale": "en", "labels": { "group": "infrastructure", "capability/containers": 2.51, "capability/devops": 3.16 }, "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", "audience": [ "enterprise", "provider" ], "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- **Patch and update service**\n- **Operational support** while it runs\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": 315, "solutions": [ { "ref": "solutions/vmware/vmware-cloud-foundation/vks", "score": "0.40" }, { "ref": "solutions/hpe/hpe-morpheus", "score": "0.39" }, { "ref": "solutions/igel/igel-managed-containers", "score": "0.39" }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/application-services", "score": "0.38" } ], "alsoLike": [ { "ref": "experts/louis-kern", "score": "0.60" }, { "ref": "posts/breaking-and-fixing-gitlab", "score": "0.54" }, { "ref": "experts/tobias-waelti", "score": "0.52" } ], "experts": [ { "ref": "experts/louis-kern", "score": "0.60" }, { "ref": "experts/tobias-waelti", "score": "0.52" }, { "ref": "experts/marco-mattei", "score": "0.35" } ], "search": "/en/search.json" }}
apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "linux-container"locale = "en"[metadata.labels]group = "infrastructure""capability/containers" = 2.51"capability/devops" = 3.16[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"audience = ["enterprise", "provider"]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[[spec.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- **Patch and update service**- **Operational support** while it runs- **Open-source and licensed software** on Linux- **Automation**- **DevOps**- **Training**'''[[spec.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.'''[[spec.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 = 315search = "/en/search.json"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/vks"score = "0.40"[[status.solutions]]ref = "solutions/hpe/hpe-morpheus"score = "0.39"[[status.solutions]]ref = "solutions/igel/igel-managed-containers"score = "0.39"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/addon/application-services"score = "0.38"[[status.alsoLike]]ref = "experts/louis-kern"score = "0.60"[[status.alsoLike]]ref = "posts/breaking-and-fixing-gitlab"score = "0.54"[[status.alsoLike]]ref = "experts/tobias-waelti"score = "0.52"[[status.experts]]ref = "experts/louis-kern"score = "0.60"[[status.experts]]ref = "experts/tobias-waelti"score = "0.52"[[status.experts]]ref = "experts/marco-mattei"score = "0.35"
<?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.51</entry> <entry key="capability/devops">3.16</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> <audience> <item>enterprise</item> <item>provider</item> </audience> <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> <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- **Patch and update service**- **Operational support** while it runs- **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> </spec> <status> <corpus>315</corpus> <solutions> <item> <ref>solutions/vmware/vmware-cloud-foundation/vks</ref> <score>0.40</score> </item> <item> <ref>solutions/hpe/hpe-morpheus</ref> <score>0.39</score> </item> <item> <ref>solutions/igel/igel-managed-containers</ref> <score>0.39</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/addon/application-services</ref> <score>0.38</score> </item> </solutions> <alsoLike> <item> <ref>experts/louis-kern</ref> <score>0.60</score> </item> <item> <ref>posts/breaking-and-fixing-gitlab</ref> <score>0.54</score> </item> <item> <ref>experts/tobias-waelti</ref> <score>0.52</score> </item> </alsoLike> <experts> <item> <ref>experts/louis-kern</ref> <score>0.60</score> </item> <item> <ref>experts/tobias-waelti</ref> <score>0.52</score> </item> <item> <ref>experts/marco-mattei</ref> <score>0.35</score> </item> </experts> <search>/en/search.json</search> </status></manifest>
# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "linux-container", "locale": "en", "labels": { "group": "infrastructure", "capability/containers": 2.51, "capability/devops": 3.16, }, "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", "audience": ["enterprise", "provider"], "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" "- **Patch and update service**\n" "- **Operational support** while it runs\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\n" "agreement: how long a release is maintained, how security updates are delivered, and who is\n" "accountable when something does not work. An estate without a support agreement is cheaper,\n" "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\n" "the operating system, it is the orchestration: how an image reaches the environment, who is\n" "allowed to put it there, and what happens on an update.\n" "\n" "Those questions are organisational. Which is exactly why training often gets you further\n" "than another platform does." ), }, ], }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/vmware/vmware-cloud-foundation/vks", "score": "0.40", }, { "ref": "solutions/hpe/hpe-morpheus", "score": "0.39", }, { "ref": "solutions/igel/igel-managed-containers", "score": "0.39", }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/application-services", "score": "0.38", }, ], "alsoLike": [ { "ref": "experts/louis-kern", "score": "0.60", }, { "ref": "posts/breaking-and-fixing-gitlab", "score": "0.54", }, { "ref": "experts/tobias-waelti", "score": "0.52", }, ], "experts": [ { "ref": "experts/louis-kern", "score": "0.60", }, { "ref": "experts/tobias-waelti", "score": "0.52", }, { "ref": "experts/marco-mattei", "score": "0.35", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))
# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Service' metadata = [ordered]@{ name = 'linux-container' locale = 'en' labels = [ordered]@{ group = 'infrastructure' 'capability/containers' = 2.51 'capability/devops' = 3.16 } annotations = [ordered]@{ 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 = [ordered]@{ title = 'Linux and Containers' group = 'infrastructure' audience = @('enterprise', 'provider') 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 = @( [ordered]@{ 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- **Patch and update service**- **Operational support** while it runs- **Open-source and licensed software** on Linux- **Automation**- **DevOps**- **Training**'@ } [ordered]@{ 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.'@ } [ordered]@{ 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 = [ordered]@{ corpus = 315 solutions = @( [ordered]@{ ref = 'solutions/vmware/vmware-cloud-foundation/vks' score = '0.40' } [ordered]@{ ref = 'solutions/hpe/hpe-morpheus' score = '0.39' } [ordered]@{ ref = 'solutions/igel/igel-managed-containers' score = '0.39' } [ordered]@{ ref = 'solutions/vmware/vmware-cloud-foundation/addon/application-services' score = '0.38' } ) alsoLike = @( [ordered]@{ ref = 'experts/louis-kern' score = '0.60' } [ordered]@{ ref = 'posts/breaking-and-fixing-gitlab' score = '0.54' } [ordered]@{ ref = 'experts/tobias-waelti' score = '0.52' } ) experts = @( [ordered]@{ ref = 'experts/louis-kern' score = '0.60' } [ordered]@{ ref = 'experts/tobias-waelti' score = '0.52' } [ordered]@{ ref = 'experts/marco-mattei' score = '0.35' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32
// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": map[string]any{ "name": "linux-container", "locale": "en", "labels": map[string]any{ "group": "infrastructure", "capability/containers": 2.51, "capability/devops": 3.16, }, "annotations": map[string]any{ "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": map[string]any{ "title": "Linux and Containers", "group": "infrastructure", "audience": []any{"enterprise", "provider"}, "order": 5, "tags": []any{"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": []any{ map[string]any{ "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" + "- **Patch and update service**\n" + "- **Operational support** while it runs\n" + "- **Open-source and licensed software** on Linux\n" + "- **Automation**\n" + "- **DevOps**\n" + "- **Training**", }, map[string]any{ "heading": "

Where the decision actually gets made

", "body": "At the distribution, and not for technical reasons. The day-to-day difference is the support\n" + "agreement: how long a release is maintained, how security updates are delivered, and who is\n" + "accountable when something does not work. An estate without a support agreement is cheaper,\n" + "until it is not.", }, map[string]any{ "heading": "

The move to containers

", "body": "Anyone running Linux already holds most of the knowledge containers need. What is new is not\n" + "the operating system, it is the orchestration: how an image reaches the environment, who is\n" + "allowed to put it there, and what happens on an update.\n" + "\n" + "Those questions are organisational. Which is exactly why training often gets you further\n" + "than another platform does.", }, }, }, "status": map[string]any{ "corpus": 315, "solutions": []any{ map[string]any{ "ref": "solutions/vmware/vmware-cloud-foundation/vks", "score": "0.40", }, map[string]any{ "ref": "solutions/hpe/hpe-morpheus", "score": "0.39", }, map[string]any{ "ref": "solutions/igel/igel-managed-containers", "score": "0.39", }, map[string]any{ "ref": "solutions/vmware/vmware-cloud-foundation/addon/application-services", "score": "0.38", }, }, "alsoLike": []any{ map[string]any{ "ref": "experts/louis-kern", "score": "0.60", }, map[string]any{ "ref": "posts/breaking-and-fixing-gitlab", "score": "0.54", }, map[string]any{ "ref": "experts/tobias-waelti", "score": "0.52", }, }, "experts": []any{ map[string]any{ "ref": "experts/louis-kern", "score": "0.60", }, map[string]any{ "ref": "experts/tobias-waelti", "score": "0.52", }, map[string]any{ "ref": "experts/marco-mattei", "score": "0.35", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}
// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Service", metadata: { name: "linux-container", locale: "en", labels: { group: "infrastructure", "capability/containers": 2.51, "capability/devops": 3.16, }, 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", audience: ["enterprise", "provider"], 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" + "- **Patch and update service**\n" + "- **Operational support** while it runs\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\n" + "agreement: how long a release is maintained, how security updates are delivered, and who is\n" + "accountable when something does not work. An estate without a support agreement is cheaper,\n" + "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\n" + "the operating system, it is the orchestration: how an image reaches the environment, who is\n" + "allowed to put it there, and what happens on an update.\n" + "\n" + "Those questions are organisational. Which is exactly why training often gets you further\n" + "than another platform does.", }, ], }, status: { corpus: 315, solutions: [ { ref: "solutions/vmware/vmware-cloud-foundation/vks", score: "0.40", }, { ref: "solutions/hpe/hpe-morpheus", score: "0.39", }, { ref: "solutions/igel/igel-managed-containers", score: "0.39", }, { ref: "solutions/vmware/vmware-cloud-foundation/addon/application-services", score: "0.38", }, ], alsoLike: [ { ref: "experts/louis-kern", score: "0.60", }, { ref: "posts/breaking-and-fixing-gitlab", score: "0.54", }, { ref: "experts/tobias-waelti", score: "0.52", }, ], experts: [ { ref: "experts/louis-kern", score: "0.60", }, { ref: "experts/tobias-waelti", score: "0.52", }, { ref: "experts/marco-mattei", score: "0.35", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 69 lines · YAML · validated at build# 100 lines · JSON · validated at build# 105 lines · TOML · validated at build# 121 lines · XML · validated at build# 121 lines · Python · read back at build, equals the JSON record# 118 lines · PowerShell · read back at build, equals the JSON record# 127 lines · Go · read back at build, equals the JSON record# 112 lines · JavaScript · read back at build, equals the JSON record · served at /en/services/linux-container.md

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.51 DevOps 3.16
04Solutions
02Capabilities
315Corpus

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
  • Patch and update service
  • Operational support while it runs
  • 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.52

Marco Mattei

Senior System Engineer

DevOpsContainers
0.35
Maybe you? Take a look at our open roles.

You might also like

Person 0.60

Louis Kern
Post 0.54

Breaking and Fixing
Person 0.52

Tobias Wälti

Cookies and external services

We want to know how our pages are used. For that we rely on Google Analytics, on Google Ads and HubSpot for marketing, and on Google Maps for directions. None of it loads before you agree, and you can change your choice at any time under “Privacy settings” in the footer.

Controller: soulTec AG, Ueberlandstrasse 1, 8600 Dübendorf. Privacy policy