OCI workload execution

Stackie runs local Kubernetes OCI workloads with the pinned upstream runc runtime and CNI plugins. Kubernetes and CRI are independently buildable first-party plugins; neither reimplements a container runtime. The plugins submit typed workload requests through a descriptor-declared, identity-bound workload capability. There is no public HTTP endpoint for this authority.

Canonical Stackie blocks and OCI images remain separate. Block requests are revalidated against the current mocker.images catalog evidence. OCI requests must reference a verified, immutable Mocker root filesystem and pass Stackied’s complete policy conversion before runc or CNI starts. Unsupported security, device, namespace, resource, network, or lifecycle semantics fail closed rather than being silently weakened.

Runtime commands are executed without a shell, with absolute pinned binaries, controlled environment variables, bounded output, owned paths, and process-start identity checks that prevent PID-reuse mistakes. Interactive containers use runc’s console-socket descriptor contract; the retained pseudo-terminal is the same stream used for attach and CRI logs.