tank-os is a Fedora bootc image that packages OpenClaw as a rootless Podman workload into a bootable, updateable Linux operating system. The project leverages bootc technology to transform a container image into a complete OS image suitable for VMs, cloud deployments, or physical devices. By bundling the OpenClaw runtime, host operating system, Quadlet units, CLI shim, and upgrade mechanisms together as a single OCI container image, tank-os creates a self-contained appliance that boots consistently across multiple machines.
The core value proposition of tank-os centers on simplifying OpenClaw deployment and management. Rather than managing OpenClaw separately from the host OS, tank-os treats them as a unified system. Users publish a single bootc container image that can be built into cloud images, VM disks, or device images, ensuring every booted machine runs the same rootless OpenClaw service. The architecture maintains separation between immutable OS components managed through bootc and mutable user data, with OpenClaw state stored in the openclaw user's home directory, API keys managed through rootless Podman's secret store, and SSH access configured per instance.
The project addresses several practical deployment scenarios. It enables local demonstrations that mirror cloud production environments, supports lab and device fleets where each machine runs its own OpenClaw interface, and provides sandboxed OpenClaw hosts with mostly read-only, image-managed operating systems. The bootc integration enables transactional updates instead of ad hoc package management, per-machine secrets through Podman rather than baked-in credentials, and rapid rollback and rebuild cycles during OpenClaw host integration development.
tank-os maintains the familiar Fedora user experience despite its appliance nature. Users SSH into machines as the openclaw user, edit OpenClaw configuration files in standard locations under the home directory, interact with OpenClaw through a host CLI wrapper, and rely on systemd and Podman to maintain service availability. For test and demo deployments, the openclaw user receives passwordless sudo access to simplify local setup and bootc update testing. Production deployments can restrict OpenClaw to run as an unprivileged service user with separate administrative accounts or tightly scoped sudo policies for OS management and updates.
The repository is written primarily in Shell and classified as an operating system and OS development project with connections to bootloader, kernel, memory management, and multitasking concerns. It shares contributors with the kyuz0/amd-strix-halo-toolboxes repository. The project maintains responsive issue and pull request handling, with a median response latency of 35.9 hours across tracked items.
Documentation guides users through building the image, configuring login access, using the OpenClaw CLI, setting up model provider keys, and configuring service-gator. The project references upstream bootc documentation for conceptual understanding and day-2 operations, points to the Podman Desktop BootC extension and bootc-image-builder for disk image construction, and provides specific guidance for Podman Desktop and macOS VM deployments including SSH port discovery and guest IP configuration.
