Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is consumed, how a sidecar or init container changes runtime state, or which route resolves to which live container. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
Start a fresh conversation. Replace the highlighted placeholders.
Use competition-container-runtime to Use competition-container-runtime 在已由 ctf-sandbox-orchestrator 确立授权 CTF 实验室范围后，比较[Compose/Kubernetes 清单与已脱敏的运行时、挂载和进程证据]，离线报告从静态意图到实际消费者行为最早可证实的偏离，并保留紧凑证据链；请用简体中文输出，不进行集群或容器变更、密钥提取、提权、逃逸或实时访问。
Required inputs
[Compose/Kubernetes 清单与已脱敏的运行时、挂载和进程证据]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: competition-container-runtimedescription: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is consumed, how a sidecar or init container changes runtime state, or which route resolves to which live container. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
Competition Container Runtime
Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.
Use this skill when the challenge is really about what the live container or pod is doing now, not what the checked-in manifest claims it should do.
Reply in Simplified Chinese unless the user explicitly requests English.
Quick Start
Split intent from reality: manifest, image, startup, live mount, live route, live process.
Map host -> proxy -> container or pod -> mounted volume -> consuming process.
Keep secrets, rendered config, init output, and sidecar output separate from static manifests.
Prove one minimal live path from mounted or injected state to reachable behavior.
Reproduce the effect with the smallest runtime-specific chain.
Workflow
1. Map The Live Runtime
Compare compose or kube manifests against running containers, pods, mounted volumes, env, sidecars, init containers, and entrypoints.
Identify which process actually consumes the mounted secret, rendered config, or shared volume output.
Record whether the decisive state is image-baked, env-injected, mounted later, or written by an init/sidecar process.
3. Report The Runtime Deviation
State the earliest point where live runtime diverges from checked-in intent.
Keep one compact evidence chain from manifest or compose intent to live consumer behavior.
Read This Reference
Load references/container-runtime.md for the runtime checklist, mount-chain checklist, and common live-vs-static pitfalls.
If the hard part is kube API permissions, service-account trust, RBAC edges, admission mutations, or controller-created workload drift, prefer $competition-k8s-control-plane.
If the hard part is Host-header routing, path-prefix rewriting, or route-to-service mapping across nodes, prefer $competition-runtime-routing.
If the hard part is proving container-to-host crossover, kernel attack-surface preconditions, or stable escape primitives, prefer $competition-kernel-container-escape.
If the hard part is replaying Linux secrets, socket trust edges, or host-to-host pivots after container foothold, prefer $competition-linux-credential-pivot.
What To Preserve
Compose/Kubernetes fragments tied to live mounts or routes
Container IDs, pod names, mount paths, sidecar outputs, rendered config paths, and consuming processes
The exact route or file path that becomes reachable only at runtime