Skip to content

About

Linux system-container runtime with RAM and filesystem checkpoints, independent forks, pause and resume. Built on Sysbox and CRIU.

Topics

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Factorybox

A Linux runtime for development Sandboxes. Checkpoint a running environment, pause it to release RAM, resume its processes, or fork an independent copy of its memory and filesystem.

Factorybox combines pinned Sysbox and CRIU with a Go lifecycle controller. Each Sandbox can run a private Docker daemon. No KVM or custom kernel required. Open Software Factory uses it for coding agents and development environments.

Why system containers

Development needs services, tools and Docker, often on nodes without hardware virtualization. Sysbox provides that environment. Factorybox adds checkpoints, forks and recorded operations so interrupted work can recover without guessing who owns its resources.

Containers gVisor MicroVMs Factorybox
Kernel Shared Userspace kernel Separate guest kernel Shared, user namespaces
Hardware virtualization No No Required No
Memory checkpoint Additional tooling Supported Runtime-dependent Built in
Node setup Container runtime Sandbox runtime VMM and virtualization Privileged worker Pod

The worker is privileged and shares the node kernel. Keep each worker in one trust domain and give mutually untrusted tenants separate nodes. Cross-node RAM migration is not supported.

How it works

flowchart LR
    consumer[CLI / Factory] --> controller[Go controller]
    controller --> sysbox[Sysbox]
    controller --> criu[CRIU]
    sysbox --> sandbox[Sandbox / private Docker]
    criu <--> sandbox
    criu <--> store[(RAM / filesystem / records)]
    controller <--> store
Loading

The controller records intent, completion and resource ownership. Pinned patches handle Sysbox's virtual filesystem state and CRIU's nested Docker namespaces and OverlayFS restores. Source versions, hashes and patches.

Measured performance

Ten warm cycles measured 4.07 s median pause and 2.99 s median resume to a healthy App. All ten preserved the process, memory and counters. The worker ran two Node containers and 256 MiB of random App memory, limited to 3 CPU / 3 GiB on a Ryzen 7 4800U node with k3s. Times include Kubernetes transport; they are not cold-start times. Samples and method.

Install and check

Signed workers for Linux arm64 and amd64 are at ghcr.io/maxcodefaster/factorybox-worker:v0.1.0-beta.1. The Factory chart pins the worker image and executable hash for each architecture and documents admission and recovery.

Portable source checks:

git clone https://github.com/maxcodefaster/factorybox.git
cd factorybox
mise trust && mise install
mise exec -- python3 tools/check.py

Native builds and checks use the Factory commands factorybox:build, runtime:conformance and factorybox:publish. AGENTS.md holds contributor rules.

Report bugs in GitHub Issues and vulnerabilities through SECURITY.md. Original code is Apache-2.0. Upstream components keep their own licenses; see LICENSING.md and NOTICE.

About

Linux system-container runtime with RAM and filesystem checkpoints, independent forks, pause and resume. Built on Sysbox and CRIU.

Topics

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages