Kataglyphis-ContainerHub documentation

Multi-stage Linux container images for GPU development stacks, a slim nginx webserver, and a Windows build image.

• Multi-stage Linux images for reproducible caching

• Windows toolchain container for CI and local builds

• Optional media and Android layers for specialized workloads

Choose the guide that matches the task you want to do: inspect the image catalog, run a local Linux image, build cross-architecture artifacts, enable GPU variants, use runtime services, or build the Windows image.

Project Overview

Published images, repository image chain, feature snapshot, dependencies, and useful tools.

Project Overview

Linux Build Basics

Local runs, multi-arch builds, and sequential nerdctl builds.

Linux Build Basics

Linux Cross Builds

Additive cross-compiler lane, SDK rootfs artifacts, runtime artifacts, and manifest publishing.

Linux Cross Builds

Linux Accelerator Images

NVIDIA, AMD, and Torch variants on top of the standard Linux image chain.

Linux Accelerator Images

Runtime Services and Streaming

Webserver, display forwarding, Raspberry Pi camera notes, and WebRTC signalling and streaming.

Runtime Services and Streaming

Windows Build Performance

Making container builds incremental: what works, what does not, and why.

Windows Container Build Performance

Windows Build Image

Windows container build command, antivirus warning, and memory notes.

Windows Build Image

Project Information

Prerequisites, installation, tests, roadmap, troubleshooting, contribution, contact, and references.

Project Information

Third-Party Licenses

Complete list of bundled software components, their versions, repositories, and licenses.

Third-Party Software & Licenses

Linux image flow

The Linux container stack is intentionally split into reusable stages so BuildKit can cache stable layers and rebuild only the slice you changed.

For the full image chain, see Project Overview. For local and multi-arch build commands, see Linux Build Basics.

Common development targets:

nerdctl build -f linux/Dockerfile.base -t local/kataglyphis:base .
nerdctl build -f linux/Dockerfile.toolchain -t local/kataglyphis:compiler .
nerdctl build -f linux/Dockerfile.sdk -t local/kataglyphis:sdk .
nerdctl build -f linux/Dockerfile.media -t local/kataglyphis:media .
nerdctl build -f linux/Dockerfile.android -t local/kataglyphis:android .
nerdctl build -f linux/Dockerfile.torch -t local/kataglyphis:latest .

Contents:

• Project Overview
  • About The Project
  • Published Images and Tag Hints
  • Images in This Repository
  • Linux Image Chain
  • What You Get
  • Key Features
• Linux Build Basics
  • Image Hierarchy
  • Build Flow
  • Rootless Build Networking (host tuning)
  • Caching Layers (what is cached where)
  • Build
  • Optional Ubuntu Apt Mirror Workaround
  • Multi-Arch Build
  • Consumer bash libraries (linux/scripts/lib/)
• Linux Cross Builds
  • Cross-Compiler builder (nerdctl, amd64 host; amd64/arm64/riscv64 targets)
  • Recommended: digest-pinned orchestrator (build-cross-chain.sh)
  • Manual staged build (low-level reference)
  • SDK rootfs artifacts (first host-side build step)
  • Cross packaging to multi-arch manifest (experimental)
  • Centralized Version Management
  • Five Critical Fixes To Maintain
  • Cross env contract
• Linux Accelerator Images
  • Optional NVIDIA GPU image chain
  • NVIDIA GPU Build (Linux)
  • Torch Add-on (Linux)
  • AMD GPU Build (Linux)
• Runtime Services and Streaming
  • Webserver (Linux)
  • Run with frontend display support
  • Raspberry Pi Camera
  • WebRTC Streaming
• Windows Build Image
  • Source Patch Policy
  • Component Build Matrix
  • Prerequisites
  • Build Commands
  • nerdctl lane (admin): run, inspect, build
  • Stevedore Setup Fixes
  • Running the Image
  • Smoke Testing
  • Windows Script Reference
  • Refactor Backlog (Windows container chain)
• Fresh Windows Host Bring-Up (BK lane + repo gates)
  • Phase A — One-time host provisioning [admin]
  • Phase B — Repo checkout + gate tooling [non-admin]
  • Phase C — Build-service tuning [admin]
  • Phase D — Per-boot / per-run checks
  • Phase E — First build + verification
  • Classic-lane fallback
• Windows Container Build Performance
  • Result
  • Transports: how to set up both
  • What works: reuse one container
  • What does not work
  • The image does not fit on C:, and that is the default
  • Gotchas that cost real time
  • Reusable implementation
  • Applying this elsewhere
• GitHub CLI: Reading and Fixing Pipeline Status
  • Install and PATH
  • Reading pipeline status
  • Finding out WHY a run failed
  • Periodic checking
  • Scope

Operations & Reference:

• Cross-build verification & failure-class catalog
• Build parallelism & per-job memory calibration
• Build resource monitoring
• Code Quality Tooling (clang-format, clang-tidy, cmake-format)
• Adopting ContainerHub in a New Project
• Agentic Loop Build Matrix
• Agentic Loop Module (WindowsAgenticLoop.Common.psm1)
• Refactoring backlog — OPEN items only, ordered by execution batch
• Upstreaming: add -nostdinc++ to libstdc++ src/c++23 (Canadian-cross std module)
• Upstream issue draft — file at microsoft/hcsshim (cross-reference moby/buildkit)
• CI Build Triggers (commit-message opt-ins)
• Rancher Desktop: the supported way to run Linux containers on Windows
• Project Information
• Third-Party Software & Licenses