mirror of
https://github.com/nubenetes/awesome-kubernetes.git
synced 2026-07-12 18:00:37 +00:00
4233 lines
140 KiB
HTML
4233 lines
140 KiB
HTML
|
||
<!doctype html>
|
||
<html lang="en" class="no-js">
|
||
<head>
|
||
|
||
<meta charset="utf-8">
|
||
<meta name="viewport" content="width=device-width,initial-scale=1">
|
||
|
||
<meta name="description" content="Enterprise-grade curated portal for the modern Cloud Native ecosystem. High-density, AI-driven selection of top-tier resources.">
|
||
|
||
|
||
<meta name="author" content="Nubenetes">
|
||
|
||
|
||
<link rel="canonical" href="https://nubenetes.com/container-managers/">
|
||
|
||
|
||
<link rel="prev" href="../web-servers/">
|
||
|
||
|
||
<link rel="next" href="../docker/">
|
||
|
||
|
||
|
||
|
||
|
||
<link rel="icon" href="../images/favicon-ultra.png">
|
||
<meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.7.6">
|
||
|
||
|
||
|
||
<title>Container Managers - Nubenetes V2 | The AI's Cut</title>
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../assets/stylesheets/main.484c7ddc.min.css">
|
||
|
||
|
||
<link rel="stylesheet" href="../assets/stylesheets/palette.ab4e12ef.min.css">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:300,300i,400,400i,700,700i%7CRoboto+Mono:400,400i,700,700i&display=fallback">
|
||
<style>:root{--md-text-font:"Roboto";--md-code-font:"Roboto Mono"}</style>
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;700&display=swap">
|
||
|
||
<link rel="stylesheet" href="../static/extra.css">
|
||
|
||
<link rel="stylesheet" href="../static/v2_elite.css?v=2.3.44">
|
||
|
||
<script>__md_scope=new URL("..",location),__md_hash=e=>[...e].reduce(((e,_)=>(e<<5)-e+_.charCodeAt(0)),0),__md_get=(e,_=localStorage,t=__md_scope)=>JSON.parse(_.getItem(t.pathname+"."+e)),__md_set=(e,_,t=localStorage,a=__md_scope)=>{try{t.setItem(a.pathname+"."+e,JSON.stringify(_))}catch(e){}}</script>
|
||
|
||
|
||
|
||
|
||
|
||
</head>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<body dir="ltr" data-md-color-scheme="slate" data-md-color-primary="custom" data-md-color-accent="custom">
|
||
|
||
|
||
<input class="md-toggle" data-md-toggle="drawer" type="checkbox" id="__drawer" autocomplete="off">
|
||
<input class="md-toggle" data-md-toggle="search" type="checkbox" id="__search" autocomplete="off">
|
||
<label class="md-overlay" for="__drawer"></label>
|
||
<div data-md-component="skip">
|
||
|
||
|
||
<a href="#container-runtimesmanagers-base-images-and-container-tools-podman-buildah-and-skopeo" class="md-skip">
|
||
Skip to content
|
||
</a>
|
||
|
||
</div>
|
||
<div data-md-component="announce">
|
||
|
||
</div>
|
||
|
||
<div data-md-color-scheme="default" data-md-component="outdated" hidden>
|
||
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<header class="md-header md-header--shadow md-header--lifted" data-md-component="header">
|
||
<nav class="md-header__inner md-grid" aria-label="Header">
|
||
<a href=".." title="Nubenetes V2 | The AI's Cut" class="md-header__button md-logo" aria-label="Nubenetes V2 | The AI's Cut" data-md-component="logo">
|
||
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M12 8a3 3 0 0 0 3-3 3 3 0 0 0-3-3 3 3 0 0 0-3 3 3 3 0 0 0 3 3m0 3.54C9.64 9.35 6.5 8 3 8v11c3.5 0 6.64 1.35 9 3.54 2.36-2.19 5.5-3.54 9-3.54V8c-3.5 0-6.64 1.35-9 3.54"/></svg>
|
||
|
||
</a>
|
||
<label class="md-header__button md-icon" for="__drawer">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M3 6h18v2H3zm0 5h18v2H3zm0 5h18v2H3z"/></svg>
|
||
</label>
|
||
<div class="md-header__title" data-md-component="header-title">
|
||
<div class="md-header__ellipsis">
|
||
<div class="md-header__topic">
|
||
<span class="md-ellipsis">
|
||
Nubenetes V2 | The AI's Cut
|
||
</span>
|
||
</div>
|
||
<div class="md-header__topic" data-md-component="header-topic">
|
||
<span class="md-ellipsis">
|
||
|
||
Container Managers
|
||
|
||
</span>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<form class="md-header__option" data-md-component="palette">
|
||
|
||
|
||
|
||
|
||
<input class="md-option" data-md-color-media="" data-md-color-scheme="slate" data-md-color-primary="custom" data-md-color-accent="custom" aria-label="Switch to light mode" type="radio" name="__palette" id="__palette_0">
|
||
|
||
<label class="md-header__button md-icon" title="Switch to light mode" for="__palette_1" hidden>
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M12 1 3 5v6c0 5.55 3.84 10.74 9 12 5.16-1.26 9-6.45 9-12V5z"/></svg>
|
||
</label>
|
||
|
||
|
||
|
||
|
||
|
||
<input class="md-option" data-md-color-media="" data-md-color-scheme="default" data-md-color-primary="custom" data-md-color-accent="custom" aria-label="Switch to dark mode" type="radio" name="__palette" id="__palette_1">
|
||
|
||
<label class="md-header__button md-icon" title="Switch to dark mode" for="__palette_0" hidden>
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M21 11c0 5.55-3.84 10.74-9 12-5.16-1.26-9-6.45-9-12V5l9-4 9 4zm-9 10c3.75-1 7-5.46 7-9.78V6.3l-7-3.12L5 6.3v4.92C5 15.54 8.25 20 12 21m-3-6.67c1.76 2.17 5.13 2.24 6.97.07.23-.27.08-.68-.26-.74a4.5 4.5 0 0 1-3.18-2.2 4.5 4.5 0 0 1-.32-3.86.453.453 0 0 0-.51-.6c-3.34.62-4.89 4.61-2.7 7.33"/></svg>
|
||
</label>
|
||
|
||
|
||
</form>
|
||
|
||
|
||
|
||
<script>var palette=__md_get("__palette");if(palette&&palette.color){if("(prefers-color-scheme)"===palette.color.media){var media=matchMedia("(prefers-color-scheme: light)"),input=document.querySelector(media.matches?"[data-md-color-media='(prefers-color-scheme: light)']":"[data-md-color-media='(prefers-color-scheme: dark)']");palette.color.media=input.getAttribute("data-md-color-media"),palette.color.scheme=input.getAttribute("data-md-color-scheme"),palette.color.primary=input.getAttribute("data-md-color-primary"),palette.color.accent=input.getAttribute("data-md-color-accent")}for(var[key,value]of Object.entries(palette.color))document.body.setAttribute("data-md-color-"+key,value)}</script>
|
||
|
||
|
||
|
||
|
||
|
||
<label class="md-header__button md-icon" for="__search">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M9.5 3A6.5 6.5 0 0 1 16 9.5c0 1.61-.59 3.09-1.56 4.23l.27.27h.79l5 5-1.5 1.5-5-5v-.79l-.27-.27A6.52 6.52 0 0 1 9.5 16 6.5 6.5 0 0 1 3 9.5 6.5 6.5 0 0 1 9.5 3m0 2C7 5 5 7 5 9.5S7 14 9.5 14 14 12 14 9.5 12 5 9.5 5"/></svg>
|
||
</label>
|
||
<div class="md-search" data-md-component="search" role="dialog">
|
||
<label class="md-search__overlay" for="__search"></label>
|
||
<div class="md-search__inner" role="search">
|
||
<form class="md-search__form" name="search">
|
||
<input type="text" class="md-search__input" name="query" aria-label="Search" placeholder="Search" autocapitalize="off" autocorrect="off" autocomplete="off" spellcheck="false" data-md-component="search-query" required>
|
||
<label class="md-search__icon md-icon" for="__search">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M9.5 3A6.5 6.5 0 0 1 16 9.5c0 1.61-.59 3.09-1.56 4.23l.27.27h.79l5 5-1.5 1.5-5-5v-.79l-.27-.27A6.52 6.52 0 0 1 9.5 16 6.5 6.5 0 0 1 3 9.5 6.5 6.5 0 0 1 9.5 3m0 2C7 5 5 7 5 9.5S7 14 9.5 14 14 12 14 9.5 12 5 9.5 5"/></svg>
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg>
|
||
</label>
|
||
<nav class="md-search__options" aria-label="Search">
|
||
|
||
<a href="javascript:void(0)" class="md-search__icon md-icon" title="Share" aria-label="Share" data-clipboard data-clipboard-text="" data-md-component="search-share" tabindex="-1">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M18 16.08c-.76 0-1.44.3-1.96.77L8.91 12.7c.05-.23.09-.46.09-.7s-.04-.47-.09-.7l7.05-4.11c.54.5 1.25.81 2.04.81a3 3 0 0 0 3-3 3 3 0 0 0-3-3 3 3 0 0 0-3 3c0 .24.04.47.09.7L8.04 9.81C7.5 9.31 6.79 9 6 9a3 3 0 0 0-3 3 3 3 0 0 0 3 3c.79 0 1.5-.31 2.04-.81l7.12 4.15c-.05.21-.08.43-.08.66 0 1.61 1.31 2.91 2.92 2.91s2.92-1.3 2.92-2.91A2.92 2.92 0 0 0 18 16.08"/></svg>
|
||
</a>
|
||
|
||
<button type="reset" class="md-search__icon md-icon" title="Clear" aria-label="Clear" tabindex="-1">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M19 6.41 17.59 5 12 10.59 6.41 5 5 6.41 10.59 12 5 17.59 6.41 19 12 13.41 17.59 19 19 17.59 13.41 12z"/></svg>
|
||
</button>
|
||
</nav>
|
||
|
||
<div class="md-search__suggest" data-md-component="search-suggest"></div>
|
||
|
||
</form>
|
||
<div class="md-search__output">
|
||
<div class="md-search__scrollwrap" tabindex="0" data-md-scrollfix>
|
||
<div class="md-search-result" data-md-component="search-result">
|
||
<div class="md-search-result__meta">
|
||
Initializing search
|
||
</div>
|
||
<ol class="md-search-result__list" role="presentation"></ol>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="md-header__source">
|
||
<a href="https://github.com/nubenetes/awesome-kubernetes" title="Go to repository" class="md-source" data-md-component="source">
|
||
<div class="md-source__icon md-icon">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512"><!--! Font Awesome Free 7.1.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2025 Fonticons, Inc.--><path d="M439.6 236.1 244 40.5c-5.4-5.5-12.8-8.5-20.4-8.5s-15 3-20.4 8.4L162.5 81l51.5 51.5c27.1-9.1 52.7 16.8 43.4 43.7l49.7 49.7c34.2-11.8 61.2 31 35.5 56.7-26.5 26.5-70.2-2.9-56-37.3L240.3 199v121.9c25.3 12.5 22.3 41.8 9.1 55-6.4 6.4-15.2 10.1-24.3 10.1s-17.8-3.6-24.3-10.1c-17.6-17.6-11.1-46.9 11.2-56v-123c-20.8-8.5-24.6-30.7-18.6-45L142.6 101 8.5 235.1C3 240.6 0 247.9 0 255.5s3 15 8.5 20.4l195.6 195.7c5.4 5.4 12.7 8.4 20.4 8.4s15-3 20.4-8.4l194.7-194.7c5.4-5.4 8.4-12.8 8.4-20.4s-3-15-8.4-20.4"/></svg>
|
||
</div>
|
||
<div class="md-source__repository">
|
||
nubenetes/awesome-kubernetes
|
||
</div>
|
||
</a>
|
||
</div>
|
||
|
||
</nav>
|
||
|
||
|
||
|
||
<nav class="md-tabs" aria-label="Tabs" data-md-component="tabs">
|
||
<div class="md-grid">
|
||
<ul class="md-tabs__list">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="https://nubenetes.com/v1/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
🔙 Back to V1 (Exhaustive)
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href=".." class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
The 2026 Vision
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../tags/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Technical Tags
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../videos/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Agentic Video Hub
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../ai-agents-mcp/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
AI
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../about/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Architectural Foundations
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../chaos-engineering/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Platform & Site Reliability
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../ansible/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Hardened Infrastructure
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../GoogleCloudPlatform/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Cloud Providers (Hyperscalers)
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../caching/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Networking & Service Mesh
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item md-tabs__item--active">
|
||
<a href="./" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
The Container Stack
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../crunchydata/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Data & Advanced Analytics
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../argo/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Engineering Pipeline
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../ChromeDevTools/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Developer Ecosystem
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../appointment-scheduling/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Career & Industry
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
</ul>
|
||
</div>
|
||
</nav>
|
||
|
||
|
||
</header>
|
||
|
||
<div class="md-container" data-md-component="container">
|
||
|
||
|
||
|
||
|
||
<main class="md-main" data-md-component="main">
|
||
<div class="md-main__inner md-grid">
|
||
|
||
|
||
|
||
<div class="md-sidebar md-sidebar--primary" data-md-component="sidebar" data-md-type="navigation" >
|
||
<div class="md-sidebar__scrollwrap">
|
||
<div class="md-sidebar__inner">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<nav class="md-nav md-nav--primary md-nav--lifted md-nav--integrated" aria-label="Navigation" data-md-level="0">
|
||
<label class="md-nav__title" for="__drawer">
|
||
<a href=".." title="Nubenetes V2 | The AI's Cut" class="md-nav__button md-logo" aria-label="Nubenetes V2 | The AI's Cut" data-md-component="logo">
|
||
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M12 8a3 3 0 0 0 3-3 3 3 0 0 0-3-3 3 3 0 0 0-3 3 3 3 0 0 0 3 3m0 3.54C9.64 9.35 6.5 8 3 8v11c3.5 0 6.64 1.35 9 3.54 2.36-2.19 5.5-3.54 9-3.54V8c-3.5 0-6.64 1.35-9 3.54"/></svg>
|
||
|
||
</a>
|
||
Nubenetes V2 | The AI's Cut
|
||
</label>
|
||
|
||
<div class="md-nav__source">
|
||
<a href="https://github.com/nubenetes/awesome-kubernetes" title="Go to repository" class="md-source" data-md-component="source">
|
||
<div class="md-source__icon md-icon">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512"><!--! Font Awesome Free 7.1.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2025 Fonticons, Inc.--><path d="M439.6 236.1 244 40.5c-5.4-5.5-12.8-8.5-20.4-8.5s-15 3-20.4 8.4L162.5 81l51.5 51.5c27.1-9.1 52.7 16.8 43.4 43.7l49.7 49.7c34.2-11.8 61.2 31 35.5 56.7-26.5 26.5-70.2-2.9-56-37.3L240.3 199v121.9c25.3 12.5 22.3 41.8 9.1 55-6.4 6.4-15.2 10.1-24.3 10.1s-17.8-3.6-24.3-10.1c-17.6-17.6-11.1-46.9 11.2-56v-123c-20.8-8.5-24.6-30.7-18.6-45L142.6 101 8.5 235.1C3 240.6 0 247.9 0 255.5s3 15 8.5 20.4l195.6 195.7c5.4 5.4 12.7 8.4 20.4 8.4s15-3 20.4-8.4l194.7-194.7c5.4-5.4 8.4-12.8 8.4-20.4s-3-15-8.4-20.4"/></svg>
|
||
</div>
|
||
<div class="md-source__repository">
|
||
nubenetes/awesome-kubernetes
|
||
</div>
|
||
</a>
|
||
</div>
|
||
|
||
<ul class="md-nav__list" data-md-scrollfix>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="https://nubenetes.com/v1/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
🔙 Back to V1 (Exhaustive)
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href=".." class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
The 2026 Vision
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../tags/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Technical Tags
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../videos/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Agentic Video Hub
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../ai-agents-mcp/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
AI
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../about/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Architectural Foundations
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../chaos-engineering/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Platform & Site Reliability
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../ansible/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Hardened Infrastructure
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../GoogleCloudPlatform/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Cloud Providers (Hyperscalers)
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../caching/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Networking & Service Mesh
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--active md-nav__item--section md-nav__item--nested">
|
||
|
||
|
||
|
||
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_11" checked>
|
||
|
||
|
||
<label class="md-nav__link" for="__nav_11" id="__nav_11_label" tabindex="">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
The Container Stack
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
</label>
|
||
|
||
<nav class="md-nav" data-md-level="1" aria-labelledby="__nav_11_label" aria-expanded="true">
|
||
<label class="md-nav__title" for="__nav_11">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
|
||
The Container Stack
|
||
|
||
|
||
</label>
|
||
<ul class="md-nav__list" data-md-scrollfix>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--active">
|
||
|
||
<input class="md-nav__toggle md-toggle" type="checkbox" id="__toc">
|
||
|
||
|
||
|
||
|
||
|
||
<label class="md-nav__link md-nav__link--active" for="__toc">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Container Managers
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
</label>
|
||
|
||
<a href="./" class="md-nav__link md-nav__link--active">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Container Managers
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<label class="md-nav__title" for="__toc">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
Table of contents
|
||
</label>
|
||
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#table-of-contents" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Table of Contents
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#application-development" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Application Development
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Application Development">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#php" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
PHP
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="PHP">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#kubernetes-integration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Kubernetes Integration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#architectural-foundations" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Architectural Foundations
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Architectural Foundations">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#kubernetes-tools" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Kubernetes Tools
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Kubernetes Tools">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#general-reference" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
General Reference
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#container-infrastructure" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Container Infrastructure
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Container Infrastructure">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#advanced-runtimes" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Advanced Runtimes
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Advanced Runtimes">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#vm-in-container" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
VM-in-Container
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#ci-cd-pipelines" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
CI-CD Pipelines
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="CI-CD Pipelines">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#pipeline-security" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Pipeline Security
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#container-engines" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Container Engines
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Container Engines">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#comparative-analysis" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Comparative Analysis
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#docker-migration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Docker Migration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#feature-highlights" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Feature Highlights
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#nested-virtualization" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Nested Virtualization
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#podman-basics" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Podman Basics
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#podman-client-setup" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Podman Client Setup
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#rootless-operations" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Rootless Operations
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#secret-management" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Secret Management
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#security-and-permissions" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Security and Permissions
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#windows-wsl2-integration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Windows WSL2 Integration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#macos-integration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
macOS Integration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#container-tooling" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Container Tooling
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Container Tooling">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#compose-comparison" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Compose Comparison
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#decompiled-engines" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Decompiled Engines
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#docker-compose-compatibility" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Docker Compose Compatibility
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#image-distribution" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Image Distribution
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#local-registries" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Local Registries
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#observability" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Observability
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#podman-compose" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Podman Compose
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#edge-orchestration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Edge Orchestration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Edge Orchestration">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#auto-updates-and-rollbacks" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Auto-Updates and Rollbacks
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#graphical-user-interfaces" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Graphical User Interfaces
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Graphical User Interfaces">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#podman-desktop" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Podman Desktop
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#podman-desktop-tools" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Podman Desktop Tools
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#image-distribution-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Image Distribution (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Image Distribution (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#ecosystem-registries" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Ecosystem Registries
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#image-optimization" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Image Optimization
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Image Optimization">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#base-images" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Base Images
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#red-hat-ubi" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Red Hat UBI
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#image-synthesis" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Image Synthesis
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Image Synthesis">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#buildkit-integration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
BuildKit Integration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#builder-comparison" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Builder Comparison
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#language-specific-builders" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Language-Specific Builders
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#industry-context" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Industry Context
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Industry Context">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#technical-discussions" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Technical Discussions
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#infrastructure-as-code" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Infrastructure as Code
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Infrastructure as Code">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#ansible-automation" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Ansible Automation
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#shell-scripting" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Shell Scripting
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#kubernetes-integration-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Kubernetes Integration (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Kubernetes Integration (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#declarative-pods" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Declarative Pods
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#manifest-translation" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Manifest Translation
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#service-orchestration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Service Orchestration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Service Orchestration">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#quadlet-integration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Quadlet Integration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#systemd-integration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Systemd Integration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#container-runtime" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Container Runtime
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Container Runtime">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#core-infrastructure" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Core Infrastructure
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Core Infrastructure">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#execution-engines" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Execution Engines
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#containerization" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Containerization
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Containerization">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#container-engines-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Container Engines (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Container Engines (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#daemonless-execution" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Daemonless Execution
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#strategy-and-standards" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Strategy and Standards
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#fundamentals" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Fundamentals
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Fundamentals">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#best-practices" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Best Practices
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#standards" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Standards
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#terminology" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Terminology
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#image-construction" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Image Construction
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Image Construction">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#security-practice" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Security Practice
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#runtimes" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Runtimes
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Runtimes">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#architectural-comparison" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Architectural Comparison
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#high-level-engines" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
High-Level Engines
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#hypervisor-based-runtimes" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Hypervisor-based Runtimes
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#kubernetes-integration-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Kubernetes Integration (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#low-level-engines" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Low-Level Engines
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#performance-optimization" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Performance Optimization
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#infrastructure" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Infrastructure
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Infrastructure">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#containerization-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Containerization (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Containerization (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#image-building" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Image Building
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#runtimes-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Runtimes (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#containers" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Containers
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Containers">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#image-building-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Image Building (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#image-management" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Image Management
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#migration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Migration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#kernel" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Kernel
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Kernel">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#resource-allocation" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Resource Allocation
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#log-management-and-diagnostics" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Log Management and Diagnostics
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Log Management and Diagnostics">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#command-line-tools" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Command Line Tools
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Command Line Tools">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#terminal-interfaces" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Terminal Interfaces
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#microservices" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Microservices
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Microservices">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#mocking-and-testing" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Mocking and Testing
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Mocking and Testing">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#podman-compose-integration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Podman Compose Integration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#platform" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Platform
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Platform">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#container-engines-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Container Engines (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Container Engines (2)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#daemonless-runtimes" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Daemonless Runtimes
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#container-security" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Container Security
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Container Security">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#oci-builders" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
OCI Builders
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../docker/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Docker
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubectl-commands/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubectl Commands
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-alternatives/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes Alternatives
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-autoscaling/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes Autoscaling
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-backup-migrations/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes Backup Migrations
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-based-devel/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes Based Devel
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-bigdata/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes Bigdata
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-client-libraries/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes Client Libraries
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-monitoring/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes Monitoring
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-on-premise/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes On Premise
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-operators-controllers/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes Operators Controllers
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-releases/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes Releases
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-storage/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes Storage
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-troubleshooting/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes Troubleshooting
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../noops/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Noops
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../ocp3/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
OCP 3
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../ocp4/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
OCP 4
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../openshift/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Openshift
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../rancher/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Rancher
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../serverless/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Serverless
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../crunchydata/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Data & Advanced Analytics
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../argo/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Engineering Pipeline
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../ChromeDevTools/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Developer Ecosystem
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../appointment-scheduling/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Career & Industry
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
</ul>
|
||
</nav>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
<div class="md-content" data-md-component="content">
|
||
|
||
<article class="md-content__inner md-typeset">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="https://github.com/nubenetes/awesome-kubernetes/edit/master/v2-docs/container-managers.md" title="Edit this page" class="md-content__button md-icon" rel="edit">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M10 20H6V4h7v5h5v3.1l2-2V8l-6-6H6c-1.1 0-2 .9-2 2v16c0 1.1.9 2 2 2h4zm10.2-7c.1 0 .3.1.4.2l1.3 1.3c.2.2.2.6 0 .8l-1 1-2.1-2.1 1-1c.1-.1.2-.2.4-.2m0 3.9L14.1 23H12v-2.1l6.1-6.1z"/></svg>
|
||
</a>
|
||
|
||
|
||
|
||
|
||
|
||
<a href="https://github.com/nubenetes/awesome-kubernetes/raw/master/v2-docs/container-managers.md" title="View source of this page" class="md-content__button md-icon">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M17 18c.56 0 1 .44 1 1s-.44 1-1 1-1-.44-1-1 .44-1 1-1m0-3c-2.73 0-5.06 1.66-6 4 .94 2.34 3.27 4 6 4s5.06-1.66 6-4c-.94-2.34-3.27-4-6-4m0 6.5a2.5 2.5 0 0 1-2.5-2.5 2.5 2.5 0 0 1 2.5-2.5 2.5 2.5 0 0 1 2.5 2.5 2.5 2.5 0 0 1-2.5 2.5M9.27 20H6V4h7v5h5v4.07c.7.08 1.36.25 2 .49V8l-6-6H6a2 2 0 0 0-2 2v16a2 2 0 0 0 2 2h4.5a8.2 8.2 0 0 1-1.23-2"/></svg>
|
||
</a>
|
||
|
||
|
||
|
||
<h1 id="container-runtimesmanagers-base-images-and-container-tools-podman-buildah-and-skopeo">Container Runtimes/Managers, Base Images and Container Tools. Podman, Buildah and Skopeo<a class="headerlink" href="#container-runtimesmanagers-base-images-and-container-tools-podman-buildah-and-skopeo" title="Permanent link">¶</a></h1>
|
||
<div class="admonition tip">
|
||
<p class="admonition-title">Nubenetes V2 Elite Portal</p>
|
||
<p>You are browsing the AI-Curated V2 Elite Edition. Looking for the exhaustive list of references? Check out the <a href="/v1/container-managers/"><strong>V1 Historical Archive</strong></a>.</p>
|
||
</div>
|
||
<div class="admonition info">
|
||
<p class="admonition-title">Architectural Context</p>
|
||
<p>Detailed reference for Container Runtimes/Managers, Base Images and Container Tools. Podman, Buildah and Skopeo in the context of The Container Stack.</p>
|
||
</div>
|
||
<h2 id="table-of-contents">Table of Contents<a class="headerlink" href="#table-of-contents" title="Permanent link">¶</a></h2>
|
||
<ol>
|
||
<li><a href="#application-development">Application Development</a></li>
|
||
<li><a href="#php">PHP</a><ul>
|
||
<li><a href="#kubernetes-integration">Kubernetes Integration</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#architectural-foundations">Architectural Foundations</a></li>
|
||
<li><a href="#kubernetes-tools">Kubernetes Tools</a><ul>
|
||
<li><a href="#general-reference">General Reference</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#container-infrastructure">Container Infrastructure</a></li>
|
||
<li><a href="#advanced-runtimes">Advanced Runtimes</a><ul>
|
||
<li><a href="#vm-in-container">VM-in-Container</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#ci-cd-pipelines">CI-CD Pipelines</a><ul>
|
||
<li><a href="#pipeline-security">Pipeline Security</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#container-engines">Container Engines</a><ul>
|
||
<li><a href="#comparative-analysis">Comparative Analysis</a></li>
|
||
<li><a href="#docker-migration">Docker Migration</a></li>
|
||
<li><a href="#feature-highlights">Feature Highlights</a></li>
|
||
<li><a href="#nested-virtualization">Nested Virtualization</a></li>
|
||
<li><a href="#podman-basics">Podman Basics</a></li>
|
||
<li><a href="#podman-client-setup">Podman Client Setup</a></li>
|
||
<li><a href="#rootless-operations">Rootless Operations</a></li>
|
||
<li><a href="#secret-management">Secret Management</a></li>
|
||
<li><a href="#security-and-permissions">Security and Permissions</a></li>
|
||
<li><a href="#windows-wsl2-integration">Windows WSL2 Integration</a></li>
|
||
<li><a href="#macos-integration">macOS Integration</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#container-tooling">Container Tooling</a><ul>
|
||
<li><a href="#compose-comparison">Compose Comparison</a></li>
|
||
<li><a href="#decompiled-engines">Decompiled Engines</a></li>
|
||
<li><a href="#docker-compose-compatibility">Docker Compose Compatibility</a></li>
|
||
<li><a href="#image-distribution">Image Distribution</a></li>
|
||
<li><a href="#local-registries">Local Registries</a></li>
|
||
<li><a href="#observability">Observability</a></li>
|
||
<li><a href="#podman-compose">Podman Compose</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#edge-orchestration">Edge Orchestration</a><ul>
|
||
<li><a href="#auto-updates-and-rollbacks">Auto-Updates and Rollbacks</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#graphical-user-interfaces">Graphical User Interfaces</a><ul>
|
||
<li><a href="#podman-desktop">Podman Desktop</a></li>
|
||
<li><a href="#podman-desktop-tools">Podman Desktop Tools</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#image-distribution-1">Image Distribution</a><ul>
|
||
<li><a href="#ecosystem-registries">Ecosystem Registries</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#image-optimization">Image Optimization</a><ul>
|
||
<li><a href="#base-images">Base Images</a></li>
|
||
<li><a href="#red-hat-ubi">Red Hat UBI</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#image-synthesis">Image Synthesis</a><ul>
|
||
<li><a href="#buildkit-integration">BuildKit Integration</a></li>
|
||
<li><a href="#builder-comparison">Builder Comparison</a></li>
|
||
<li><a href="#language-specific-builders">Language-Specific Builders</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#industry-context">Industry Context</a><ul>
|
||
<li><a href="#technical-discussions">Technical Discussions</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#infrastructure-as-code">Infrastructure as Code</a><ul>
|
||
<li><a href="#ansible-automation">Ansible Automation</a></li>
|
||
<li><a href="#shell-scripting">Shell Scripting</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#kubernetes-integration-1">Kubernetes Integration</a><ul>
|
||
<li><a href="#declarative-pods">Declarative Pods</a></li>
|
||
<li><a href="#manifest-translation">Manifest Translation</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#service-orchestration">Service Orchestration</a><ul>
|
||
<li><a href="#quadlet-integration">Quadlet Integration</a></li>
|
||
<li><a href="#systemd-integration">Systemd Integration</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#container-runtime">Container Runtime</a></li>
|
||
<li><a href="#core-infrastructure">Core Infrastructure</a><ul>
|
||
<li><a href="#execution-engines">Execution Engines</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#containerization">Containerization</a></li>
|
||
<li><a href="#container-engines-1">Container Engines</a><ul>
|
||
<li><a href="#daemonless-execution">Daemonless Execution</a></li>
|
||
<li><a href="#strategy-and-standards">Strategy and Standards</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#fundamentals">Fundamentals</a><ul>
|
||
<li><a href="#best-practices">Best Practices</a></li>
|
||
<li><a href="#standards">Standards</a></li>
|
||
<li><a href="#terminology">Terminology</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#image-construction">Image Construction</a><ul>
|
||
<li><a href="#security-practice">Security Practice</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#runtimes">Runtimes</a><ul>
|
||
<li><a href="#architectural-comparison">Architectural Comparison</a></li>
|
||
<li><a href="#high-level-engines">High-Level Engines</a></li>
|
||
<li><a href="#hypervisor-based-runtimes">Hypervisor-based Runtimes</a></li>
|
||
<li><a href="#kubernetes-integration-2">Kubernetes Integration</a></li>
|
||
<li><a href="#low-level-engines">Low-Level Engines</a></li>
|
||
<li><a href="#performance-optimization">Performance Optimization</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#infrastructure">Infrastructure</a></li>
|
||
<li><a href="#containerization-1">Containerization</a><ul>
|
||
<li><a href="#image-building">Image Building</a></li>
|
||
<li><a href="#runtimes-1">Runtimes</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#containers">Containers</a><ul>
|
||
<li><a href="#image-building-1">Image Building</a></li>
|
||
<li><a href="#image-management">Image Management</a></li>
|
||
<li><a href="#migration">Migration</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#kernel">Kernel</a><ul>
|
||
<li><a href="#resource-allocation">Resource Allocation</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#log-management-and-diagnostics">Log Management and Diagnostics</a></li>
|
||
<li><a href="#command-line-tools">Command Line Tools</a><ul>
|
||
<li><a href="#terminal-interfaces">Terminal Interfaces</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#microservices">Microservices</a></li>
|
||
<li><a href="#mocking-and-testing">Mocking and Testing</a><ul>
|
||
<li><a href="#podman-compose-integration">Podman Compose Integration</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#platform">Platform</a></li>
|
||
<li><a href="#container-engines-2">Container Engines</a><ul>
|
||
<li><a href="#daemonless-runtimes">Daemonless Runtimes</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#container-security">Container Security</a><ul>
|
||
<li><a href="#oci-builders">OCI Builders</a></li>
|
||
</ul>
|
||
</li>
|
||
</ol>
|
||
<h2 id="application-development">Application Development<a class="headerlink" href="#application-development" title="Permanent link">¶</a></h2>
|
||
<h3 id="php">PHP<a class="headerlink" href="#php" title="Permanent link">¶</a></h3>
|
||
<h4 id="kubernetes-integration">Kubernetes Integration<a class="headerlink" href="#kubernetes-integration" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2026)</strong> <a href="https://github.com/sherifabdlnaby/kubephp"><mark>sherifabdlnaby/kubephp</mark></a> <span class='md-tag md-tag--info'>⭐ 456</span> <svg class="v2-sparkline" width="50" height="15" viewBox="0 0 50 15" style="vertical-align: middle; display: inline-block; margin-left: 6px;" title="Activity Trend"><defs><linearGradient id="spark-grad-b979da19" x1="0" y1="0" x2="1" y2="0"><stop offset="0%" stop-color="rgba(34, 211, 238, 0.2)" /><stop offset="100%" stop-color="var(--md-accent-fg-color)" /></linearGradient></defs><path class="v2-sparkline-path" d="M 0 6 L 10 4 L 20 11 L 30 7 L 40 5 L 50 4" fill="none" stroke="url(#spark-grad-b979da19)" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" /><circle cx="50" cy="4" r="2" fill="var(--md-accent-fg-color)" /></svg> <span class='md-tag md-tag--warning'>[PHP CONTENT]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — KubePHP is a specialized repository detailing optimal configurations for deploying PHP applications (particularly PHP-FPM and Nginx sidecars) onto Kubernetes clusters. It addresses PHP-specific cloud-native challenges such as shared volume sessions, OPcache preloading, and graceful shutdown handling. It provides critical scaffolding and architectural advice for modernizing legacy PHP monoliths into production-grade, autoscaled microservices.</li>
|
||
</ul>
|
||
<h2 id="architectural-foundations">Architectural Foundations<a class="headerlink" href="#architectural-foundations" title="Permanent link">¶</a></h2>
|
||
<h3 id="kubernetes-tools">Kubernetes Tools<a class="headerlink" href="#kubernetes-tools" title="Permanent link">¶</a></h3>
|
||
<h4 id="general-reference">General Reference<a class="headerlink" href="#general-reference" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><a href="https://www.docker.com/products/container-runtime">Docker</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering Docker in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/javarevisited/podman-getting-started-e7fc06961994">medium: Podman: Getting Started</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium: Podman: Getting Started in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://oldgitops.medium.com/setting-up-podman-on-wsl2-in-windows-10-be2991c2d443">oldgitops.medium.com: Setting up Podman on WSL2 in Windows 10 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering oldgitops.medium.com: Setting up Podman on WSL2 in Windows 10 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/techbeatly/exploring-docker-alternative-podman-14674c990311">medium.com: Exploring Docker alternative — Podman</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com: Exploring Docker alternative — Podman in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/@raghavendraguttur/podman-containers-beginners-guide-830b931e66f4">medium.com/@raghavendraguttur: Podman Containers — Beginner’s Guide</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/@raghavendraguttur: Podman Containers — Beginner’s Guide in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://nilesh93.medium.com/replacing-docker-desktop-with-podman-and-kind-in-macos-c750581a3fda">nilesh93.medium.com: Replacing Docker Desktop with Podman and Kind in MacOS</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering nilesh93.medium.com: Replacing Docker Desktop with Podman and Kind in MacOS in the Kubernetes Tools ecosystem.</li>
|
||
</ul>
|
||
<h2 id="container-infrastructure">Container Infrastructure<a class="headerlink" href="#container-infrastructure" title="Permanent link">¶</a></h2>
|
||
<h3 id="advanced-runtimes">Advanced Runtimes<a class="headerlink" href="#advanced-runtimes" title="Permanent link">¶</a></h3>
|
||
<h4 id="vm-in-container">VM-in-Container<a class="headerlink" href="#vm-in-container" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://opensource.com/article/21/7/linux-podman">opensource.com: Run a Linux virtual machine in Podman</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — An architectural exploration of executing a nested Linux VM directly within an OCI-compliant container managed by Podman. This setup leverages nested systemd instances, enabling engineers to package legacy system-level workloads, VMs, or multi-process service layers without full VM overhead.</li>
|
||
</ul>
|
||
<h3 id="ci-cd-pipelines">CI-CD Pipelines<a class="headerlink" href="#ci-cd-pipelines" title="Permanent link">¶</a></h3>
|
||
<h4 id="pipeline-security">Pipeline Security<a class="headerlink" href="#pipeline-security" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.redhat.com/en/blog/using-container-technology-make-trusted-pipeline">Build trusted pipelines/Guards with Podman containers</a> <span class='md-tag md-tag--warning'>[YAML CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Analyzes how to design highly secure, isolated CI/CD pipelines using Podman container guards. By isolating execution steps within unprivileged container sandboxes, this architecture protects build systems and host servers from security compromises.</li>
|
||
</ul>
|
||
<h3 id="container-engines">Container Engines<a class="headerlink" href="#container-engines" title="Permanent link">¶</a></h3>
|
||
<h4 id="comparative-analysis">Comparative Analysis<a class="headerlink" href="#comparative-analysis" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.imaginarycloud.com/blog/podman-vs-docker">imaginarycloud.com: Podman vs Docker: What are the differences?</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A structured comparison detailing the architectural contrasts between Docker and Podman. It highlights the security advantages of Podman's unprivileged user execution over Docker's root-privileged centralized socket model, and maps their differences in local systemd integration.</li>
|
||
</ul>
|
||
<h4 id="docker-migration">Docker Migration<a class="headerlink" href="#docker-migration" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://developers.redhat.com/blog/2020/11/19/transitioning-from-docker-to-podman">developers.redhat.com: Transitioning from Docker to Podman 🌟</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A technical migration playbook outlining the primary CLI parity and architectural differences between Docker and Podman. It covers transitioning from a monolithic daemon to Podman's secure fork-exec runtime model, highlighting alias management, unprivileged group setups, and network mapping differences.</li>
|
||
</ul>
|
||
<h4 id="feature-highlights">Feature Highlights<a class="headerlink" href="#feature-highlights" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/podman-features-1">redhat.com: 5 Podman features to try now</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Highlights five high-impact Podman features: systemd integration, rootless execution, pod support, multiple image store locations, and advanced CLI capabilities. It helps engineers adopt cloud-native features that bypass standard Docker runtime limitations.</li>
|
||
</ul>
|
||
<h4 id="nested-virtualization">Nested Virtualization<a class="headerlink" href="#nested-virtualization" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.youtube.com/watch?app=desktop&v=OcHRWaC5tvY&feature=youtu.be&ab_channel=RedHat">youtube: Podman in Podman (Running a container within a container)</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — This architectural demonstration breaks down the security design patterns of nested virtualization, specifically running Podman within a Podman container (PinP). This technique allows unprivileged CI/CD pipelines to securely package and build OCI images without mounting the host system's root sockets, offering a safer alternative to Docker-in-Docker approaches.</li>
|
||
</ul>
|
||
<h4 id="podman-basics">Podman Basics<a class="headerlink" href="#podman-basics" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://devopscube.com/podman-tutorial-beginners">devopscube.com: Podman Tutorial For Beginners: Step by Step Guides 🌟</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — A comprehensive introductory manual providing step-by-step guidance on installing, configuring, and operating Podman container systems. It reviews Podman's daemonless, rootless architecture, standard registry authentication workflows, and how it handles container execution relative to Docker CLI.</li>
|
||
<li><strong>(2021)</strong> <a href="https://darumatic.com/blog/podman_introduction">darumatic.com: Podman - Introduction 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A foundational overview of Podman's primary features, security improvements, and daemon-free design. It explores how fork-exec architectures simplify process mapping within parent cgroups and align directly with Linux security paradigms like auditd tracking.</li>
|
||
</ul>
|
||
<h4 id="podman-client-setup">Podman Client Setup<a class="headerlink" href="#podman-client-setup" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/podman-clients-macos-windows">Podman remote clients for macOS and Windows</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — This architectural overview explains how to orchestrate containerized workloads on non-Linux platforms (macOS/Windows) using Podman remote clients. By establishing secure SSH channels to a backend Linux VM, this setup preserves Podman's trademark rootless, daemonless execution model. It eliminates local daemon management overhead while keeping host systems clean and isolated.</li>
|
||
</ul>
|
||
<h4 id="rootless-operations">Rootless Operations<a class="headerlink" href="#rootless-operations" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://opensource.com/article/22/1/run-containers-without-sudo-podman">opensource.com: Run containers on Linux without sudo in Podman</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A deep-dive on configuring host security rules to execute container networks without utilizing <code>sudo</code> privileges under Podman. It details how user namespace mappings isolate processes, ensuring that even if a container is compromised, host-level administrative access remains secure.</li>
|
||
<li><strong>(2020)</strong> <a href="https://developers.redhat.com/blog/2020/09/25/rootless-containers-with-podman-the-basics">developers.redhat.com: Rootless containers with Podman: The basics</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — This technical manual explores the implementation of rootless container technology within Podman, focusing on User Namespaces (userns) and mappings in <code>/etc/subuid</code> and <code>/etc/subgid</code>. It explains how running containers without root privileges mitigates container-breakout vulnerability risks. This architecture provides high security profiles across multi-tenant development workloads without sacrificing essential execution namespaces.</li>
|
||
</ul>
|
||
<h4 id="secret-management">Secret Management<a class="headerlink" href="#secret-management" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/new-podman-secrets-command">redhat.com: Exploring the new Podman secret command 🌟</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An in-depth look at the <code>podman secret</code> command subsystem, which manages sensitive credentials securely on the local host keyring rather than hardcoding them in images. This pattern brings Kubernetes-style secret mounting to systemd and standalone container workloads, preventing credentials leakage in microservice environments.</li>
|
||
</ul>
|
||
<h4 id="security-and-permissions">Security and Permissions<a class="headerlink" href="#security-and-permissions" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.redhat.com/en/blog/privileged-flag-container-engines">How to use the --privileged flag with container engines</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An in-depth security analysis detailing the architectural risks of running container engines with the <code>--privileged</code> flag. This guide explains how this flag bypasses Linux namespace protections and SELinux enforcement, and outlines secure configuration alternatives for hardware access.</li>
|
||
</ul>
|
||
<h4 id="windows-wsl2-integration">Windows WSL2 Integration<a class="headerlink" href="#windows-wsl2-integration" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://wbhegedus.me/running-podman-on-wsl2">wbhegedus.me: Configuring Podman for WSL2 🌟</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A technical walkthrough detailing the configuration of rootless Podman within Windows Subsystem for Linux (WSL2) without reliance on proprietary wrapper interfaces. This setup walks through systemd activation inside WSL2, setting up UID mappings, and managing remote API endpoints for a lightweight development workstation.</li>
|
||
<li><strong>(2021)</strong> <a href="https://opensource.com/article/21/10/podman-windows-wsl">opensource.com: Get podman up and running on Windows using Linux</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A detailed manual on installing and running Podman inside a manual WSL2 Linux distribution on Windows. This approach provides a customizable developer environment, walking through network bridging, storage optimizations, and subUID file mapping configurations.</li>
|
||
</ul>
|
||
<h4 id="macos-integration">macOS Integration<a class="headerlink" href="#macos-integration" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.redhat.com/en/blog/replace-docker-podman-mac-revisited">redhat.com: How to replace Docker with Podman on a Mac, revisited</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An updated architectural guide on replacing Docker Desktop with Podman on macOS. This revision covers modern updates to Podman Machine, performance-tuned mounting solutions, and port-forwarding schemes that simplify the developer experience on Apple Silicon.</li>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/replace-docker-podman-macos">redhat.com: How to replace Docker with Podman on a Mac</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An installation guide detailing how to replace Docker Desktop on macOS using the native Podman Machine subsystem, which utilizes a Fedora-based CoreOS VM in QEMU. It outlines rootless volume sharing, port-forwarding setups, and local terminal alias configuration, achieving low-overhead development environments on Mac hardware.</li>
|
||
</ul>
|
||
<h3 id="container-tooling">Container Tooling<a class="headerlink" href="#container-tooling" title="Permanent link">¶</a></h3>
|
||
<h4 id="compose-comparison">Compose Comparison<a class="headerlink" href="#compose-comparison" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://crunchtools.com/should-i-use-docker-compose-or-podman-compose-with-podman">crunchtools.com: Should I Use Docker Compose Or Podman Compose With Podman?</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — This architectural comparison contrasts the usage of Podman Compose with Docker Compose running on Podman's virtualized API socket. The synthesis recommends leveraging the Docker-compatible socket configuration in enterprise environments for high-fidelity compatibility with complex multi-container definitions.</li>
|
||
</ul>
|
||
<h4 id="decompiled-engines">Decompiled Engines<a class="headerlink" href="#decompiled-engines" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://dev.to/cedricclyburn/containers-without-docker-podman-buildah-and-skopeo-1eal">dev.to: Containers without Docker (podman, buildah, and skopeo)</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An analysis of the modular container ecosystem, detailing how monolithic Docker tasks are decomposed into specialized, unprivileged utilities: Podman for execution, Buildah for image creation, and Skopeo for registry transfer. This architecture optimizes security and performance in enterprise environments.</li>
|
||
</ul>
|
||
<h4 id="docker-compose-compatibility">Docker Compose Compatibility<a class="headerlink" href="#docker-compose-compatibility" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/podman-docker-compose">redhat.com: Using Podman and Docker Compose</a> <span class='md-tag md-tag--warning'>[YAML CONTENT]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — This technical brief details the integration of Podman with Docker Compose via the virtualization of a Docker-compatible UNIX socket (<code>podman.sock</code>). By enabling this systemd-managed service, developers can execute legacy multi-container environments defined in Docker Compose files without modification, shifting the workload under Podman's daemonless, secure execution model.</li>
|
||
<li><strong>(2021)</strong> <a href="https://www.youtube.com/watch?v=15PFfjuxtvM&ab_channel=mkdev">youtube: Podman 3 and Docker Compose - How Does the Dockerless Compose Work? 🌟</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — This video tutorial covers the REST API capabilities introduced in Podman 3 and its virtualized Docker-compatible socket. It provides step-by-step demonstrations running unmodified Docker Compose setups under Podman, illustrating the underlying socket mapping mechanics that enable seamless developer workflows.</li>
|
||
<li><strong>(2021)</strong> <a href="https://fedoramagazine.org/use-docker-compose-with-podman-to-orchestrate-containers-on-fedora">fedoramagazine.org: Use Docker Compose with Podman to Orchestrate Containers on Fedora Linux</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An implementation manual focused on configuring Docker Compose pipelines to run on Fedora Linux workstations utilizing Podman's unprivileged user sockets. It explains how to bypass typical daemon-related attack vectors while maintaining high-fidelity support for standard multi-service YAML specs.</li>
|
||
</ul>
|
||
<h4 id="image-distribution">Image Distribution<a class="headerlink" href="#image-distribution" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://www.tecmint.com/manage-containers-using-podman-in-rhel">tecmint.com: How to Manage Containers Using Podman and Skopeo in RHEL 8</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — This guide outlines container management workflows in RHEL environments using Podman for execution alongside Skopeo for remote image inspection and registry manipulation. Skopeo's design enables pipelines to inspect remote container layers and copy images directly between registries without local pulling or local daemon storage overhead. This approach optimizes CI/CD pipeline storage and network efficiency.</li>
|
||
</ul>
|
||
<h4 id="local-registries">Local Registries<a class="headerlink" href="#local-registries" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://thenewstack.io/tutorial-host-a-local-podman-image-registry">thenewstack.io: Tutorial: Host a Local Podman Image Registry 🌟</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — An operations tutorial detailing how to host and secure a local container image registry on a Podman development node. This blueprint outlines container networking setups, systemd integration, and storage mounting strategies, facilitating offline local image building and rapid microservice prototyping loops.</li>
|
||
</ul>
|
||
<h4 id="observability">Observability<a class="headerlink" href="#observability" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/container-information-podman">redhat.com: How to use Podman to get information about your containers</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Provides techniques for extracting and parsing runtime telemetry data from Podman systems using structured queries and JSON outputs. It covers tools like <code>podman inspect</code> and <code>podman stats</code> to build local monitoring solutions for microservice containers.</li>
|
||
</ul>
|
||
<h4 id="podman-compose">Podman Compose<a class="headerlink" href="#podman-compose" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://fedoramagazine.org/manage-containers-with-podman-compose">fedoramagazine.org: Manage containers with Podman Compose</a> <span class='md-tag md-tag--warning'>[PYTHON CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — This resource reviews the configuration of Podman Compose, a Python-based utility developed to interpret YAML schemas and execute local multi-container groupings. While it functions as a lightweight alternative, live grounding highlights that modern enterprise setups prefer native Docker Compose with <code>podman.sock</code> compatibility due to its deeper feature coverage.</li>
|
||
</ul>
|
||
<h3 id="edge-orchestration">Edge Orchestration<a class="headerlink" href="#edge-orchestration" title="Permanent link">¶</a></h3>
|
||
<h4 id="auto-updates-and-rollbacks">Auto-Updates and Rollbacks<a class="headerlink" href="#auto-updates-and-rollbacks" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/podman-auto-updates-rollbacks">redhat.com: How to use auto-updates and rollbacks in Podman</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores Podman's automated container lifecycle features designed for distributed edge environments. By coordinating with registry tags and systemd health checks, Podman triggers zero-touch image updates and automatic rollback workflows if service validation tests fail.</li>
|
||
</ul>
|
||
<h3 id="graphical-user-interfaces">Graphical User Interfaces<a class="headerlink" href="#graphical-user-interfaces" title="Permanent link">¶</a></h3>
|
||
<h4 id="podman-desktop">Podman Desktop<a class="headerlink" href="#podman-desktop" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://podman-desktop.io">Podman Desktop</a> <span class='md-tag md-tag--warning'>[TYPESCRIPT CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — The official product documentation for Podman Desktop, a premier enterprise-stable GUI dashboard designed to orchestrate local container runtimes and Kubernetes configurations. Key capabilities include visual multi-engine management, local cluster creation, and seamless extension integrations.</li>
|
||
<li><strong>(2022)</strong> <a href="https://developers.redhat.com/articles/2022/10/24/podman-expands-desktop">developers.redhat.com: Podman expands to the Desktop</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Introduces the official release of Podman Desktop, analyzing its architecture and how it simplifies unprivileged container management on Windows, macOS, and Linux. It covers packaging local engines and pod configuration tools.</li>
|
||
</ul>
|
||
<h4 id="podman-desktop-tools">Podman Desktop Tools<a class="headerlink" href="#podman-desktop-tools" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://iongion.github.io/podman-desktop-companion">iongion.github.io: Podman Desktop Companion 🌟</a> <span class='md-tag md-tag--warning'>[TYPESCRIPT CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Outlines an early community-driven Electron GUI companion built to manage Podman containers and networks visually. Live grounding notes that this community initiative has largely been succeeded by the official, enterprise-stable Podman Desktop application developed by Red Hat.</li>
|
||
</ul>
|
||
<h3 id="image-distribution-1">Image Distribution (1)<a class="headerlink" href="#image-distribution-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="ecosystem-registries">Ecosystem Registries<a class="headerlink" href="#ecosystem-registries" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://catalog.redhat.com/en/software/containers/explore">Red Hat Ecosystem Catalog</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — The access portal to the Red Hat Ecosystem Catalog, providing a registry of verified, security-scanned container images. This resource is an enterprise-stable source for deploying secure database runtimes, middleware, and application frameworks on production clusters.</li>
|
||
</ul>
|
||
<h3 id="image-optimization">Image Optimization<a class="headerlink" href="#image-optimization" title="Permanent link">¶</a></h3>
|
||
<h4 id="base-images">Base Images<a class="headerlink" href="#base-images" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://iximiuz.com/en/posts/containers-making-images-better">iximiuz.com: In Pursuit of Better Container Images: Alpine, Distroless, Apko, Chisel, DockerSlim, oh my!</a> <span class='md-tag md-tag--warning'>[GO CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A deep technical comparison of minimalist base image architectures (apko, Distroless, Chisel, DockerSlim) and their role in shrinking microservice attack surfaces. This guide walks through the trade-offs between packaging minimum system packages and compiling entirely distroless, binary-only configurations.</li>
|
||
<li><strong>(2021)</strong> <a href="https://developers.redhat.com/blog/2021/04/13/how-to-pick-the-right-container-base-image">developers.redhat.com: How to pick the right container base image</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Presents a decision matrix to help system architects choose the correct container base image. Evaluates security requirements, language dependencies, distribution sizes, and long-term support obligations across Alpine, Debian, and Red Hat UBI configurations.</li>
|
||
</ul>
|
||
<h4 id="red-hat-ubi">Red Hat UBI<a class="headerlink" href="#red-hat-ubi" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://github.com/fatherlinux/ubi-micro">ubi-micro: RHEL tiny images to build containers 🌟</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An open-source repository dedicated to UBI-Micro, Red Hat's smallest, zero-dependency base image layer designed for extreme attack surface minimization. It contains only essential package databases and relies on host-side tools like Buildah to inject necessary microservice binaries.</li>
|
||
<li><strong>(2019)</strong> <a href="https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image">Introducing the Red Hat Universal Base Image 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An overview introducing the Red Hat Universal Base Image (UBI), designed to provide enterprise RHEL security configurations without subscription constraints. UBI delivers a reliable foundation for packaging and distributing cloud-native microservices across multi-cloud environments.</li>
|
||
<li><strong>(2019)</strong> <a href="https://developers.redhat.com/blog/2019/10/09/what-is-red-hat-universal-base-image">What is Red Hat Universal Base Image?</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Deconstructs the design of Red Hat's Universal Base Image, explaining its lifecycle, support commitments, and open redistribution model. It outlines how UBI bridges the gap between secure RHEL package dependency requirements and standard public distribution channels.</li>
|
||
<li><strong>(2019)</strong> <a href="https://developers.redhat.com/articles/ubi-faq">RH Universal Base Image FAQ</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A comprehensive FAQ resource answering technical queries regarding Red Hat UBI redistribution rights, support channels, and package installation configurations. Explains differences between standard, minimal, and micro base layers to help developers choose the right runtime footprint.</li>
|
||
</ul>
|
||
<h3 id="image-synthesis">Image Synthesis<a class="headerlink" href="#image-synthesis" title="Permanent link">¶</a></h3>
|
||
<h4 id="buildkit-integration">BuildKit Integration<a class="headerlink" href="#buildkit-integration" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://pythonspeed.com/articles/podman-buildkit">pythonspeed.com: Using Podman with BuildKit, the better Docker image builder 🌟</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An advanced technical guide exploring how to configure rootless Podman to work with BuildKit, the high-performance image compiler. This configuration combines BuildKit's aggressive layer caching and multi-stage build speed optimizations with Podman's secure, unprivileged execution profile for modern container pipelines.</li>
|
||
</ul>
|
||
<h4 id="builder-comparison">Builder Comparison<a class="headerlink" href="#builder-comparison" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://itnext.io/docker-kaniko-buildah-209abdde5f94">itnext.io: Docker, Kaniko, Buildah</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Compares Docker, Kaniko, and Buildah for image compilation in modern CI/CD setups. It highlights Buildah's capability to compile OCI images without a daemon or complex kernel privileges, making it the premier choice for Kubernetes-native build steps.</li>
|
||
</ul>
|
||
<h4 id="language-specific-builders">Language-Specific Builders<a class="headerlink" href="#language-specific-builders" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://blog.kubesimplify.com/getting-started-with-ko-a-fast-container-image-builder-for-your-go-applications">blog.kubesimplify.com: Getting started with ko: A fast container image builder for your Go applications</a> <span class='md-tag md-tag--warning'>[GO CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Evaluates <code>ko</code>, an open-source image synthesis compiler built to package Go applications without requiring Docker or a local daemon. By compiling and pushing binaries directly to registries, it simplifies Go-based microservice shipping with built-in Software Bill of Materials (SBOM) generation.</li>
|
||
</ul>
|
||
<h3 id="industry-context">Industry Context<a class="headerlink" href="#industry-context" title="Permanent link">¶</a></h3>
|
||
<h4 id="technical-discussions">Technical Discussions<a class="headerlink" href="#technical-discussions" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://kubernetespodcast.com/episode/164-podman">kubernetespodcast.com: Podman, with Daniel Walsh and Brent Baude</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An interview featuring Podman's core creators, Daniel Walsh and Brent Baude, discussing the development of daemonless container engines. They detail the platform's architectural evolution, integration with local desktop managers, and its role as a secure foundation for Kubernetes microservices deployment.</li>
|
||
</ul>
|
||
<h3 id="infrastructure-as-code">Infrastructure as Code<a class="headerlink" href="#infrastructure-as-code" title="Permanent link">¶</a></h3>
|
||
<h4 id="ansible-automation">Ansible Automation<a class="headerlink" href="#ansible-automation" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/automate-podman-ansible">redhat.com: How to automate Podman installation and deployment using Ansible 🌟</a> <span class='md-tag md-tag--warning'>[YAML CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explains how to automate enterprise deployment of rootless Podman runtimes using Ansible playbooks and certified system roles. This setup streamlines the automated rollout of subUID mappings, customized registry structures, and storage configurations across highly distributed hybrid-cloud environments.</li>
|
||
</ul>
|
||
<h4 id="shell-scripting">Shell Scripting<a class="headerlink" href="#shell-scripting" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/create-containers-podman-quickly">redhat.com: Create fast, easy, and repeatable containers with Podman and shell scripts</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Demonstrates writing reproducible, automated container management pipelines using lightweight shell scripts coupled with Podman's CLI. It covers passing dynamic configurations, parsing telemetry data, and setting up automated cleanup tasks in resource-constrained environments.</li>
|
||
</ul>
|
||
<h3 id="kubernetes-integration-1">Kubernetes Integration (1)<a class="headerlink" href="#kubernetes-integration-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="declarative-pods">Declarative Pods<a class="headerlink" href="#declarative-pods" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/podman-play-kube-updates">redhat.com: Build Kubernetes pods with Podman play kube</a> <span class='md-tag md-tag--warning'>[YAML CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Examines the <code>podman play kube</code> command, which allows Podman to parse and deploy standard Kubernetes YAML definitions locally. This capability allows engineers to test and validate multi-container Kubernetes pod networks in a lightweight, local environment without a running Kubernetes cluster.</li>
|
||
</ul>
|
||
<h4 id="manifest-translation">Manifest Translation<a class="headerlink" href="#manifest-translation" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/compose-kubernetes-podman">redhat.com: From Docker Compose to Kubernetes with Podman</a> <span class='md-tag md-tag--warning'>[YAML CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — This guide covers the migration workflow from local Docker Compose files to production-ready Kubernetes manifests using Podman's native capability <code>podman generate kube</code>. This mechanism allows engineering teams to export local container configurations directly into standardized Kubernetes Pod specifications, accelerating the orchestration of modern microservices.</li>
|
||
</ul>
|
||
<h3 id="service-orchestration">Service Orchestration<a class="headerlink" href="#service-orchestration" title="Permanent link">¶</a></h3>
|
||
<h4 id="quadlet-integration">Quadlet Integration<a class="headerlink" href="#quadlet-integration" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.redhat.com/en/blog/quadlet-podman">redhat.com/sysadmin/quadlet-podman</a> <span class='md-tag md-tag--warning'>[INI CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An in-depth review of Quadlet, a tool built into Podman that integrates container management with systemd. Quadlet reads declarative configuration files to dynamically synthesize optimized systemd service definitions, resolving complex container network and dependency issues automatically.</li>
|
||
</ul>
|
||
<h4 id="systemd-integration">Systemd Integration<a class="headerlink" href="#systemd-integration" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.tutorialworks.com/podman-systemd">tutorialworks.com: How to Start Containers Automatically, with Podman and Systemd</a> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A deep dive into container auto-start architectures utilizing systemd unit files synthesized via <code>podman generate systemd</code>. This approach leverages native Linux init systems for container lifecycle orchestration, service restart policies, dependency tracking, and journald telemetry without requiring daemon overhead.</li>
|
||
</ul>
|
||
<h2 id="container-runtime">Container Runtime<a class="headerlink" href="#container-runtime" title="Permanent link">¶</a></h2>
|
||
<h3 id="core-infrastructure">Core Infrastructure<a class="headerlink" href="#core-infrastructure" title="Permanent link">¶</a></h3>
|
||
<h4 id="execution-engines">Execution Engines<a class="headerlink" href="#execution-engines" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2026)</strong> <a href="https://github.com/containerd/containerd"><mark>containerd - An open and reliable container runtime</mark></a> <span class='md-tag md-tag--info'>⭐ 20835</span> <svg class="v2-sparkline" width="50" height="15" viewBox="0 0 50 15" style="vertical-align: middle; display: inline-block; margin-left: 6px;" title="Activity Trend"><defs><linearGradient id="spark-grad-591370f5" x1="0" y1="0" x2="1" y2="0"><stop offset="0%" stop-color="rgba(34, 211, 238, 0.2)" /><stop offset="100%" stop-color="var(--md-accent-fg-color)" /></linearGradient></defs><path class="v2-sparkline-path" d="M 0 11 L 10 12 L 20 7 L 30 9 L 40 6 L 50 4" fill="none" stroke="url(#spark-grad-591370f5)" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" /><circle cx="50" cy="4" r="2" fill="var(--md-accent-fg-color)" /></svg> <span class='md-tag md-tag--warning'>[GO CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — containerd is an industry-standard container runtime designed to be embedded into larger systems like Kubernetes. Following the deprecation of Docker's native runtime engine in Kubernetes, containerd has emerged as the de facto execution engine for production-grade orchestrators.</li>
|
||
</ul>
|
||
<h2 id="containerization">Containerization<a class="headerlink" href="#containerization" title="Permanent link">¶</a></h2>
|
||
<h3 id="container-engines-1">Container Engines (1)<a class="headerlink" href="#container-engines-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="daemonless-execution">Daemonless Execution<a class="headerlink" href="#daemonless-execution" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2018)</strong> <a href="https://github.com/containers/podman"><mark>Libpod: Library and tool for running OCI-based containers in Pods</mark></a> <span class='md-tag md-tag--info'>⭐ 31763</span> <svg class="v2-sparkline" width="50" height="15" viewBox="0 0 50 15" style="vertical-align: middle; display: inline-block; margin-left: 6px;" title="Activity Trend"><defs><linearGradient id="spark-grad-022b1447" x1="0" y1="0" x2="1" y2="0"><stop offset="0%" stop-color="rgba(34, 211, 238, 0.2)" /><stop offset="100%" stop-color="var(--md-accent-fg-color)" /></linearGradient></defs><path class="v2-sparkline-path" d="M 0 2 L 10 5 L 20 5 L 30 10 L 40 3 L 50 4" fill="none" stroke="url(#spark-grad-022b1447)" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" /><circle cx="50" cy="4" r="2" fill="var(--md-accent-fg-color)" /></svg> <span class='md-tag md-tag--warning'>[GO CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — The core engine library underlying Podman, enabling programmatic creation and lifecycle management of OCI-compliant containers and Pods. Libpod brings native Kubernetes-style multi-container 'Pod' groupings to local local environments without requiring a background orchestration API.</li>
|
||
<li><strong>(2021)</strong> <a href="https://www.youtube.com/watch?v=Za36qHbrf3g">youtube: Getting started with Podman</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A developer-oriented video walkthrough detailing installation, basic image handling, and container deployment using Podman. Explains core concepts of local rootless container security and basic networking models for developers transitioning from monolithic engine setups.</li>
|
||
<li><strong>(2020)</strong> <a href="https://podman.io/blogs/2020/06/29/podman-v2-announce.html">podmain.io: Announcing Podman v2</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — The release announcement detailing Podman v2's updated architecture, notably the introduction of a new structured REST API. This release allows remote management of containers from macOS or Windows machines, bridging compatibility barriers to match modern hybrid-development requirements.</li>
|
||
<li><strong>(2019)</strong> <a href="https://developers.redhat.com/blog/2019/02/21/podman-and-buildah-for-docker-users">developers.redhat.com: Podman and Buildah for Docker users 🌟</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — A practical handbook for developers transitionining from legacy Docker tooling to the modern Podman/Buildah stack. It walks through command mapping, registry authentications, building minimal rootless images, and deploying local Kubernetes-style multi-container YAML manifests.</li>
|
||
<li><strong>(2018)</strong> <a href="https://developers.redhat.com/blog/2018/08/29/intro-to-podman">Intro to Podman</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An introductory engineering guide presenting Podman's design philosophies. It outlines the core mechanics of running daemonless containers, using standard alias configs to replace traditional docker systems, and managing container storage within unprivileged user directories.</li>
|
||
</ul>
|
||
<h4 id="strategy-and-standards">Strategy and Standards<a class="headerlink" href="#strategy-and-standards" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2019)</strong> <a href="https://www.redhat.com/en/blog/why-red-hat-investing-cri-o-and-podman">Why Red Hat is investing in CRI-O and Podman</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A strategic analysis detailing Red Hat's engineering shift from Docker to CRI-O and Podman. It explores the security advantages of rootless architectures, the reduction of single-point-of-failure daemons, and the architectural benefits of aligning runtimes strictly to Kubernetes-compatible CRI specifications.</li>
|
||
</ul>
|
||
<h3 id="fundamentals">Fundamentals<a class="headerlink" href="#fundamentals" title="Permanent link">¶</a></h3>
|
||
<h4 id="best-practices">Best Practices<a class="headerlink" href="#best-practices" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://thenewstack.io/containers/container-best-practices-what-they-are-and-why-you-should-care">thenewstack.io: Container Best Practices: What They Are and Why You Should Care</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A comprehensive catalog of enterprise-level design guidelines for developing containerized workloads. It focuses on minimized base images, rootless execution models, multi-stage compilation patterns, environment variable isolation, and automated vulnerability scanning at the repository layer.</li>
|
||
</ul>
|
||
<h4 id="standards">Standards<a class="headerlink" href="#standards" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2015)</strong> <a href="https://opencontainers.org">OCI: Open Container Initiative</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--primary'>[DOCUMENTATION]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — The primary industry-governed specification standard for container formats and runtimes. By defining precise, cross-vendor standards for OCI Image Specifications and Runtime Specifications, it ensures complete runtime interoperability across diverse infrastructure orchestrators and container engines.</li>
|
||
</ul>
|
||
<h4 id="terminology">Terminology<a class="headerlink" href="#terminology" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2018)</strong> <a href="https://developers.redhat.com/blog/2018/02/22/container-terminology-practical-introduction">A Practical Introduction to Container Terminology</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A classic Red Hat reference guide clarifying container terms including namespaces, cgroups, images, registries, runtimes (OCI, CRI), and orchestration layers. It provides standard technical definitions required to construct, run, and manage container architectures without proprietary runtime locks.</li>
|
||
</ul>
|
||
<h3 id="image-construction">Image Construction<a class="headerlink" href="#image-construction" title="Permanent link">¶</a></h3>
|
||
<h4 id="security-practice">Security Practice<a class="headerlink" href="#security-practice" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://www.redhat.com/en/blog/be-careful-when-pulling-images-short-name">redhat.com: Be careful when pulling images by short name</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A critical security advisory highlighting the risks of short-name image pulling. It describes spoofing and poisoning vectors, explaining how to force container engines to use fully-qualified domain names (FQDN) to guarantee image provenance and registry safety.</li>
|
||
</ul>
|
||
<h3 id="runtimes">Runtimes<a class="headerlink" href="#runtimes" title="Permanent link">¶</a></h3>
|
||
<h4 id="architectural-comparison">Architectural Comparison<a class="headerlink" href="#architectural-comparison" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2019)</strong> <a href="https://www.inovex.de/de/blog/containers-docker-containerd-nabla-kata-firecracker">inovex.de: Welcome To The Container Jungle: Docker vs. containerd vs. Nabla vs. Kata vs. Firecracker and more! 🌟</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An elite technical taxonomy comparing standard container runtimes (runc, containerd) against secure micro-VM and sandbox hypervisors (Kata, Firecracker, Nabla). It explains execution isolation boundaries, hypervisor overhead, and performance implications across edge, multi-tenant, and classic enterprise workloads.</li>
|
||
</ul>
|
||
<h4 id="high-level-engines">High-Level Engines<a class="headerlink" href="#high-level-engines" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2017)</strong> <a href="https://containerd.io">containerd.io</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--primary'>[DOCUMENTATION]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Official home page and core design documentation for the containerd runtime engine. It details the modular runtime API architecture, gRPC interfaces, client-side abstractions, and storage drivers that enable major cloud providers and local workstations to run containers at massive scale.</li>
|
||
</ul>
|
||
<h4 id="hypervisor-based-runtimes">Hypervisor-based Runtimes<a class="headerlink" href="#hypervisor-based-runtimes" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://github.com/kubernetes-retired/frakti"><mark>Frakti</mark></a> <span class='md-tag md-tag--info'>⭐ 675</span> <svg class="v2-sparkline" width="50" height="15" viewBox="0 0 50 15" style="vertical-align: middle; display: inline-block; margin-left: 6px;" title="Activity Trend"><defs><linearGradient id="spark-grad-56c4b85f" x1="0" y1="0" x2="1" y2="0"><stop offset="0%" stop-color="rgba(34, 211, 238, 0.2)" /><stop offset="100%" stop-color="var(--md-accent-fg-color)" /></linearGradient></defs><path class="v2-sparkline-path" d="M 0 12 L 10 4 L 20 12 L 30 12 L 40 6 L 50 6" fill="none" stroke="url(#spark-grad-56c4b85f)" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" /><circle cx="50" cy="6" r="2" fill="var(--md-accent-fg-color)" /></svg> <span class='md-tag md-tag--warning'>[GO CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — Critical Live Grounding: Built originally to support hypervisor-based Container Runtime Interfaces (CRI), Frakti has been officially retired and archived by the Kubernetes organization. Modern environments utilize container-native VM interfaces like Kata Containers or Firecracker integrated directly into containerd.</li>
|
||
</ul>
|
||
<h4 id="kubernetes-integration-2">Kubernetes Integration (2)<a class="headerlink" href="#kubernetes-integration-2" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2024)</strong> <a href="https://kubernetes.io/docs/setup/production-environment/container-runtimes">Kubernetes.io: Container runtimes</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--primary'>[DOCUMENTATION]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — The official Kubernetes documentation detailing installation and integration patterns for CRI-compliant container runtimes. It provides step-by-step production setup configurations for containerd and CRI-O, detailing necessary kernel parameters, socket configurations, and systemd driver alignments.</li>
|
||
<li><strong>(2017)</strong> <a href="https://cri-o.io">cri-o.io</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--primary'>[DOCUMENTATION]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — The official home of CRI-O, an optimized Container Runtime Interface (CRI) designed specifically and exclusively for Kubernetes. CRI-O avoids overhead by supporting only OCI-compliant runtimes, removing unnecessary client CLI abstractions to deliver minimum-footprint workload execution.</li>
|
||
</ul>
|
||
<h4 id="low-level-engines">Low-Level Engines<a class="headerlink" href="#low-level-engines" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2019)</strong> <a href="https://github.com/containers/crun"><mark>crun</mark></a> <span class='md-tag md-tag--info'>⭐ 3964</span> <svg class="v2-sparkline" width="50" height="15" viewBox="0 0 50 15" style="vertical-align: middle; display: inline-block; margin-left: 6px;" title="Activity Trend"><defs><linearGradient id="spark-grad-381ce51b" x1="0" y1="0" x2="1" y2="0"><stop offset="0%" stop-color="rgba(34, 211, 238, 0.2)" /><stop offset="100%" stop-color="var(--md-accent-fg-color)" /></linearGradient></defs><path class="v2-sparkline-path" d="M 0 2 L 10 11 L 20 5 L 30 8 L 40 9 L 50 3" fill="none" stroke="url(#spark-grad-381ce51b)" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" /><circle cx="50" cy="3" r="2" fill="var(--md-accent-fg-color)" /></svg> <span class='md-tag md-tag--warning'>[C CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — A high-performance, lightweight, and low-memory-footprint OCI runtime written completely in C. It serves as an ultra-fast alternative to Go-based runc, offering native support for advanced Linux features such as cgroups v2, user namespaces, and direct system call mapping.</li>
|
||
<li><strong>(2017)</strong> <a href="https://github.com/containers/conmon"><mark>Conmon</mark></a> <span class='md-tag md-tag--info'>⭐ 481</span> <svg class="v2-sparkline" width="50" height="15" viewBox="0 0 50 15" style="vertical-align: middle; display: inline-block; margin-left: 6px;" title="Activity Trend"><defs><linearGradient id="spark-grad-7964601d" x1="0" y1="0" x2="1" y2="0"><stop offset="0%" stop-color="rgba(34, 211, 238, 0.2)" /><stop offset="100%" stop-color="var(--md-accent-fg-color)" /></linearGradient></defs><path class="v2-sparkline-path" d="M 0 5 L 10 8 L 20 10 L 30 3 L 40 12 L 50 11" fill="none" stroke="url(#spark-grad-7964601d)" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" /><circle cx="50" cy="11" r="2" fill="var(--md-accent-fg-color)" /></svg> <span class='md-tag md-tag--warning'>[C CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — An essential, daemonless container monitor written in C, used primarily by Podman and CRI-O. Conmon supervises container lifecycles, capturing standard output/error streams, tracking exit codes, and managing attachment sockets while maintaining a negligible host resource overhead.</li>
|
||
<li><strong>(2015)</strong> <a href="https://github.com/opencontainers/runc"><mark>runc</mark></a> <span class='md-tag md-tag--info'>⭐ 13282</span> <svg class="v2-sparkline" width="50" height="15" viewBox="0 0 50 15" style="vertical-align: middle; display: inline-block; margin-left: 6px;" title="Activity Trend"><defs><linearGradient id="spark-grad-498fc206" x1="0" y1="0" x2="1" y2="0"><stop offset="0%" stop-color="rgba(34, 211, 238, 0.2)" /><stop offset="100%" stop-color="var(--md-accent-fg-color)" /></linearGradient></defs><path class="v2-sparkline-path" d="M 0 2 L 10 12 L 20 4 L 30 2 L 40 2 L 50 5" fill="none" stroke="url(#spark-grad-498fc206)" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" /><circle cx="50" cy="5" r="2" fill="var(--md-accent-fg-color)" /></svg> <span class='md-tag md-tag--warning'>[GO CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — The canonical, low-level container runtime engine built in compliance with the OCI specification. Originally contributed by Docker, runc directly spawns and runs containers on Linux by interfacing with namespaces, cgroups, and capabilities without relying on overhead daemons.</li>
|
||
</ul>
|
||
<h4 id="performance-optimization">Performance Optimization<a class="headerlink" href="#performance-optimization" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://scrivano.org/posts/2022-10-21-the-journey-to-speed-up-oci-containers">scrivano.org: the journey to speed up running OCI containers</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An exceptional technical post investigating performance optimization avenues for OCI containers. It explores the historical startup bottlenecks of container initialization and deep dives into storage drivers, container startup phases, and runtime improvements inside tools like crun.</li>
|
||
</ul>
|
||
<h2 id="infrastructure">Infrastructure<a class="headerlink" href="#infrastructure" title="Permanent link">¶</a></h2>
|
||
<h3 id="containerization-1">Containerization (1)<a class="headerlink" href="#containerization-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="image-building">Image Building<a class="headerlink" href="#image-building" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2026)</strong> <a href="https://blog.alexellis.io/building-containers-without-docker">blog.alexellis.io: Building containers without Docker 🌟</a> <span class='md-tag md-tag--warning'>[MARKDOWN CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Written by cloud-native expert Alex Ellis, this post explores build tools (such as BuildKit, Buildah, and Kaniko) that compile container images without relying on a local Docker daemon. It unpacks the benefits of using non-docker setups inside Kubernetes CI/CD runner environments, avoiding Docker-in-Docker (DinD) security compromises. It serves as an essential manual for modern cloud pipeline designs.</li>
|
||
</ul>
|
||
<h4 id="runtimes-1">Runtimes (1)<a class="headerlink" href="#runtimes-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2026)</strong> <a href="https://build5nines.com/what-is-podman-and-how-does-it-compare-to-docker">What is Podman and How Does it Compare to Docker?</a> <span class='md-tag md-tag--warning'>[MARKDOWN CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An architectural comparison analyzing the structural differences between Docker and Podman. It highlights Podman's daemonless, rootless-by-default execution model and explains how this design reduces security attack vectors compared to Docker's centralized daemon. It also details Podman's native support for pod-like multi-container groupings, easing transitions toward Kubernetes.</li>
|
||
</ul>
|
||
<h3 id="containers">Containers<a class="headerlink" href="#containers" title="Permanent link">¶</a></h3>
|
||
<h4 id="image-building-1">Image Building (1)<a class="headerlink" href="#image-building-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2026)</strong> <a href="https://github.com/containers/buildah"><mark>github.com/containers/buildah</mark></a> <span class='md-tag md-tag--info'>⭐ 8795</span> <svg class="v2-sparkline" width="50" height="15" viewBox="0 0 50 15" style="vertical-align: middle; display: inline-block; margin-left: 6px;" title="Activity Trend"><defs><linearGradient id="spark-grad-1af19895" x1="0" y1="0" x2="1" y2="0"><stop offset="0%" stop-color="rgba(34, 211, 238, 0.2)" /><stop offset="100%" stop-color="var(--md-accent-fg-color)" /></linearGradient></defs><path class="v2-sparkline-path" d="M 0 8 L 10 13 L 20 9 L 30 8 L 40 8 L 50 5" fill="none" stroke="url(#spark-grad-1af19895)" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" /><circle cx="50" cy="5" r="2" fill="var(--md-accent-fg-color)" /></svg> <span class='md-tag md-tag--warning'>[GO CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — The official GitHub repository for Buildah, containing the core Go source code for building daemonless OCI container images. Live Grounding confirms its active role as a standard engine within Kubernetes environments, particularly Red Hat OpenShift, allowing secure rootless image construction. It is highly valued for its ability to create scratch images containing only runtime-essential binaries, dramatically reducing final image attack surfaces.</li>
|
||
<li><strong>(2021)</strong> <a href="https://developers.redhat.com/blog/2021/01/11/getting-started-with-buildah">developers.redhat.com: Getting started with Buildah</a> <span class='md-tag md-tag--warning'>[N/A CONTENT]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — A comprehensive Red Hat Developers guide detailing the architectural transition from Dockerfile-based workflows to Buildah commands. It provides deep insights into script-driven image creation, showing engineers how to build nested filesystems directly inside OCI containers. The guide is highly practical for migrating complex legacy enterprise builds into lightweight Kubernetes-native deployment artifacts.</li>
|
||
</ul>
|
||
<h4 id="image-management">Image Management<a class="headerlink" href="#image-management" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2026)</strong> <a href="https://github.com/containers/skopeo"><mark>Skopeo</mark></a> <span class='md-tag md-tag--info'>⭐ 10891</span> <svg class="v2-sparkline" width="50" height="15" viewBox="0 0 50 15" style="vertical-align: middle; display: inline-block; margin-left: 6px;" title="Activity Trend"><defs><linearGradient id="spark-grad-6c5aa3ec" x1="0" y1="0" x2="1" y2="0"><stop offset="0%" stop-color="rgba(34, 211, 238, 0.2)" /><stop offset="100%" stop-color="var(--md-accent-fg-color)" /></linearGradient></defs><path class="v2-sparkline-path" d="M 0 7 L 10 12 L 20 6 L 30 12 L 40 11 L 50 5" fill="none" stroke="url(#spark-grad-6c5aa3ec)" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" /><circle cx="50" cy="5" r="2" fill="var(--md-accent-fg-color)" /></svg> <span class='md-tag md-tag--warning'>[GO CONTENT]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — Skopeo is an industry-standard command-line tool designed to perform operations on container images and image registries without requiring local container storage or engines. Architects leverage Skopeo to inspect remote manifest details, sign images, and sync packages directly between registries (e.g., from Docker Hub to ECR). Live Grounding confirms it as a vital utility in production CI/CD security scanning and compliance loops.</li>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/promoting-container-images-between-registries-with-skopeo">Promoting container images between registries with skopeo</a> <span class='md-tag md-tag--warning'>[N/A CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An official Red Hat technical article showcasing optimal architectures for promoting container images between registries using Skopeo. It details operational patterns to eliminate the 'docker pull' and 'docker push' steps in secure multi-environment CI/CD deployment gates. This methodology significantly reduces deployment time and prevents disk space exhaustion in worker nodes.</li>
|
||
</ul>
|
||
<h4 id="migration">Migration<a class="headerlink" href="#migration" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.youtube.com/watch?app=desktop&v=Fl0iLoAMdzc&ab_channel=AndrewMalkov">youtube: How to live without Docker for developers - Part 1 | Migration from Docker to Buildah and Podman</a> <span class='md-tag md-tag--warning'>[N/A CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A video-based tutorial guiding developers through migration from Docker to Podman and Buildah, detailing how to live without a daemon. It contrasts performance profiles, daemon socket vulnerabilities, and tool-chain integrations. Highly recommended for system architects looking to secure local environments and standardize on OCI-compliant developer workflows.</li>
|
||
</ul>
|
||
<h3 id="kernel">Kernel<a class="headerlink" href="#kernel" title="Permanent link">¶</a></h3>
|
||
<h4 id="resource-allocation">Resource Allocation<a class="headerlink" href="#resource-allocation" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://labs.iximiuz.com/tutorials/controlling-process-resources-with-cgroups">Controlling Process Resources with Linux Control Groups (cgroups)</a> <span class='md-tag md-tag--warning'>[C/BASH CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A system-level deep dive explaining Linux control groups (cgroups v1/v2). Demonstrates how Kubernetes translates resource limits/requests in YAML manifests to cgroup system boundaries, enforcing CPU and memory quotas.</li>
|
||
</ul>
|
||
<h2 id="log-management-and-diagnostics">Log Management and Diagnostics<a class="headerlink" href="#log-management-and-diagnostics" title="Permanent link">¶</a></h2>
|
||
<h3 id="command-line-tools">Command Line Tools<a class="headerlink" href="#command-line-tools" title="Permanent link">¶</a></h3>
|
||
<h4 id="terminal-interfaces">Terminal Interfaces<a class="headerlink" href="#terminal-interfaces" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://github.com/ynqa/bul">bul: Interactive TUI for Exploring Kubernetes Container Logs</a> <span class='md-tag md-tag--info'>⭐ 16</span> <svg class="v2-sparkline" width="50" height="15" viewBox="0 0 50 15" style="vertical-align: middle; display: inline-block; margin-left: 6px;" title="Activity Trend"><defs><linearGradient id="spark-grad-b8d76944" x1="0" y1="0" x2="1" y2="0"><stop offset="0%" stop-color="rgba(34, 211, 238, 0.2)" /><stop offset="100%" stop-color="var(--md-accent-fg-color)" /></linearGradient></defs><path class="v2-sparkline-path" d="M 0 8 L 10 6 L 20 11 L 30 8 L 40 11 L 50 9" fill="none" stroke="url(#spark-grad-b8d76944)" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" /><circle cx="50" cy="9" r="2" fill="var(--md-accent-fg-color)" /></svg> <span class='md-tag md-tag--warning'>[GO CONTENT]</span> 🌟 <span class='md-tag md-tag--critical'>[LEGACY]</span> — An interactive Terminal User Interface (TUI) written in Go designed to query and stream local Kubernetes container logs. Live Grounding Note: Because development has remained inactive for years, it is considered legacy; modern engineers typically use tools like K9s or Stern in active production.</li>
|
||
</ul>
|
||
<h2 id="microservices">Microservices<a class="headerlink" href="#microservices" title="Permanent link">¶</a></h2>
|
||
<h3 id="mocking-and-testing">Mocking and Testing<a class="headerlink" href="#mocking-and-testing" title="Permanent link">¶</a></h3>
|
||
<h4 id="podman-compose-integration">Podman Compose Integration<a class="headerlink" href="#podman-compose-integration" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://developers.redhat.com/blog/2021/04/22/using-podman-compose-with-microcks-a-cloud-native-api-mocking-and-testing-tool">developers.redhat.com: Using Podman Compose with Microcks: A cloud-native API mocking and testing tool</a> <span class='md-tag md-tag--warning'>[YAML CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Demonstrates executing Microcks, a cloud-native API mocking and testing tool, with Podman Compose in unprivileged host environments. This integration enables developers to simulate OpenAPI, gRPC, and AsyncAPI services locally without the overhead or security risks of managing a complex virtualized Docker daemon.</li>
|
||
</ul>
|
||
<h2 id="platform">Platform<a class="headerlink" href="#platform" title="Permanent link">¶</a></h2>
|
||
<h3 id="container-engines-2">Container Engines (2)<a class="headerlink" href="#container-engines-2" title="Permanent link">¶</a></h3>
|
||
<h4 id="daemonless-runtimes">Daemonless Runtimes<a class="headerlink" href="#daemonless-runtimes" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2026)</strong> <a href="https://podman.io"><mark>podman</mark></a> <span class='md-tag md-tag--warning'>[GO CONTENT]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — Podman delivers a daemonless container engine framework for executing, managing, and building OCI containers. Rootless orchestration patterns are native to Podman, allowing seamless integration with Linux systemd configurations.</li>
|
||
</ul>
|
||
<h3 id="container-security">Container Security<a class="headerlink" href="#container-security" title="Permanent link">¶</a></h3>
|
||
<h4 id="oci-builders">OCI Builders<a class="headerlink" href="#oci-builders" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2026)</strong> <a href="https://buildah.io"><mark>buildah</mark></a> <span class='md-tag md-tag--warning'>[GO CONTENT]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — Buildah specializes in crafting OCI-compliant container images without requiring a background container daemon. It enables fine-grained Layer management, dramatically reducing the security footprint of target images by keeping build tools outside the final layers.</li>
|
||
</ul>
|
||
<hr />
|
||
<p>💡 <strong>Explore Related:</strong> <a href="../kubernetes-storage/">Kubernetes Storage</a> | <a href="../kubernetes-alternatives/">Kubernetes Alternatives</a> | <a href="../kubernetes-client-libraries/">Kubernetes Client Libraries</a></p>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
</article>
|
||
</div>
|
||
|
||
|
||
<script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script>
|
||
</div>
|
||
|
||
<button type="button" class="md-top md-icon" data-md-component="top" hidden>
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M13 20h-2V8l-5.5 5.5-1.42-1.42L12 4.16l7.92 7.92-1.42 1.42L13 8z"/></svg>
|
||
Back to top
|
||
</button>
|
||
|
||
</main>
|
||
|
||
<footer class="md-footer">
|
||
|
||
<div class="md-footer-meta md-typeset">
|
||
<div class="md-footer-meta__inner md-grid">
|
||
<div class="md-copyright">
|
||
|
||
<div class="md-copyright__highlight">
|
||
Copyright © 2026 Nubenetes Agentic Intelligence
|
||
</div>
|
||
|
||
|
||
Made with
|
||
<a href="https://squidfunk.github.io/mkdocs-material/" target="_blank" rel="noopener">
|
||
Material for MkDocs
|
||
</a>
|
||
|
||
</div>
|
||
|
||
|
||
<div class="md-social">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<a href="https://github.com/nubenetes/awesome-kubernetes" target="_blank" rel="noopener" title="github.com" class="md-social__link">
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><!--! Font Awesome Free 7.1.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2025 Fonticons, Inc.--><path d="M173.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6m-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3m44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9M252.8 8C114.1 8 8 113.3 8 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C436.2 457.8 504 362.9 504 252 504 113.3 391.5 8 252.8 8M105.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1m-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7m32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1m-11.4-14.7c-1.6 1-1.6 3.6 0 5.9s4.3 3.3 5.6 2.3c1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2"/></svg>
|
||
</a>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<a href="https://twitter.com/nubenetes" target="_blank" rel="noopener" title="twitter.com" class="md-social__link">
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><!--! Font Awesome Free 7.1.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2025 Fonticons, Inc.--><path d="M459.4 151.7c.3 4.5.3 9.1.3 13.6 0 138.7-105.6 298.6-298.6 298.6-59.5 0-114.7-17.2-161.1-47.1 8.4 1 16.6 1.3 25.3 1.3 49.1 0 94.2-16.6 130.3-44.8-46.1-1-84.8-31.2-98.1-72.8 6.5 1 13 1.6 19.8 1.6 9.4 0 18.8-1.3 27.6-3.6-48.1-9.7-84.1-52-84.1-103v-1.3c14 7.8 30.2 12.7 47.4 13.3-28.3-18.8-46.8-51-46.8-87.4 0-19.5 5.2-37.4 14.3-53C87.4 130.8 165 172.4 252.1 176.9c-1.6-7.8-2.6-15.9-2.6-24C249.5 95.1 296.3 48 354.4 48c30.2 0 57.5 12.7 76.7 33.1 23.7-4.5 46.5-13.3 66.6-25.3-7.8 24.4-24.4 44.8-46.1 57.8 21.1-2.3 41.6-8.1 60.4-16.2-14.3 20.8-32.2 39.3-52.6 54.3"/></svg>
|
||
</a>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<a href="https://www.linkedin.com/groups/1937212/" target="_blank" rel="noopener" title="www.linkedin.com" class="md-social__link">
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512"><!--! Font Awesome Free 7.1.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2025 Fonticons, Inc.--><path d="M416 32H31.9C14.3 32 0 46.5 0 64.3v383.4C0 465.5 14.3 480 31.9 480H416c17.6 0 32-14.5 32-32.3V64.3c0-17.8-14.4-32.3-32-32.3M135.4 416H69V202.2h66.5V416zM102.2 96a38.5 38.5 0 1 1 0 77 38.5 38.5 0 1 1 0-77m282.1 320h-66.4V312c0-24.8-.5-56.7-34.5-56.7-34.6 0-39.9 27-39.9 54.9V416h-66.4V202.2h63.7v29.2h.9c8.9-16.8 30.6-34.5 62.9-34.5 67.2 0 79.7 44.3 79.7 101.9z"/></svg>
|
||
</a>
|
||
|
||
</div>
|
||
|
||
</div>
|
||
</div>
|
||
</footer>
|
||
|
||
</div>
|
||
<div class="md-dialog" data-md-component="dialog">
|
||
<div class="md-dialog__inner md-typeset"></div>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
<script id="__config" type="application/json">{"annotate": null, "base": "..", "features": ["navigation.tabs", "navigation.tabs.sticky", "navigation.top", "navigation.tracking", "navigation.sections", "navigation.expand", "navigation.indexes", "search.suggest", "search.highlight", "search.share", "content.code.copy", "content.action.view", "content.action.edit", "content.tooltips", "navigation.prune", "toc.integrate"], "search": "../assets/javascripts/workers/search.2c215733.min.js", "tags": null, "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}, "version": {"provider": "mike"}}</script>
|
||
|
||
|
||
<script src="../assets/javascripts/bundle.79ae519e.min.js"></script>
|
||
|
||
<script src="../static/v2_filter.js"></script>
|
||
|
||
|
||
</body>
|
||
</html> |