Podos A lightweight container platform Early development · not released

Overview

Status and roadmap

Podos is built in milestones. Version 0.1 is the single-node proof of concept; it is finished when the five-minute test passes on a fresh cloud server with a real domain, measured with a stopwatch.

Version 0.1 milestones

Milestone Content Status
M0 Foundations: architecture decisions, development VM, test tooling Available
M1 Registry client and verified blob store, state store with encrypted secrets, manifest parser and CLI skeleton Available
M2 Run containers: setup, daemon, env, secret, deploy from an image, ps, logs, down; containers survive a daemon restart Available
M3 Reachable and self-healing: networks and DNS, built-in ingress with TLS, health checks, rolling updates and rollback, restart and reboot recovery, volumes, published ports, API tokens, podos login and contexts Available on the main branch, tested and wired into podos deploy
M4 Integration and hardening: end-to-end tests, fixes from the reviews, node limits and disk guard, firewall detection (Docker, ufw, firewalld), always-blocked cloud metadata addresses, ACME directory and CA options, state database backup before a migration Available on the main branch
M5 Build on the server from local source with BuildKit, install script, systemd unit, upgrade and uninstall Available on the main branch

What each part means for you

Available (M0 to M5)

Available means the feature is in the code on the main branch. There are still no release binaries: you build podos from source. The install script (M5) needs a published release. The features were tested in the Linux development VM.

See Limits of this version for what Podos does not do.

Added with M3, all wired into podos deploy:

Feature Manifest key or command
A private network per project and environment; services reach each other by name (automatic); podos setup --network-pool, --strict-egress, --allow-egress
Built-in HTTPS proxy on ports 80 and 443 with TLS modes auto, self-signed, off, cert:<name> domains, tls; podos cert; podos setup --acme-email, --ingress
Host ports opened to a service publish
Persistent data directories per environment volumes; podos down --delete-volumes
Restart after a crash and after a reboot restart, (automatic)
Health checks (http, tcp), rolling updates and automatic rollback health; podos releases
READY and RESTARTS columns in podos ps podos ps
HTTPS API for remote use, with a certificate from the internal CA podos daemon --listen, --tls-name
Scoped, revocable API tokens; the first admin token from podos setup podos token, podos ca fingerprint
Login with CA pinning, named contexts, podos whoami podos login, podos context, --context
A manifest environment bound to a context, with confirmation [environment.prod] context = "…"
Release history podos releases
Create an environment without setting a value podos env create
A warning for literal values that look like secrets lint_ignore

Added with M4:

Feature Manifest key or command
End-to-end tests for update, failed health check, rollback, daemon kill and reboot (tests)
Fixes from the reviews, for example a new replica on a reused address that was unreachable (automatic)
All containers together capped at the server's memory minus a reserve and at 80% of the process limit; oversized resources.memory refused podos daemon --system-reserve-memory
Deploys and image pulls refused on a nearly full disk podos daemon --min-free-disk
Docker, ufw and firewalld detected on forwarded and incoming traffic, with the exact commands podos setup, daemon log
One message for a port that cannot be published; a port taken later by the host is skipped at start and shown in podos ps publish
Cloud metadata addresses always blocked (automatic)
Let's Encrypt staging or a private ACME CA podos daemon --acme-directory, --acme-ca-file
Backup of the state database before a schema migration state.db.before-v<N>

tls = "auto" (Let's Encrypt) has only been tested against a test ACME server, not yet against the real Let's Encrypt service.

Still planned for the same area, not built: exec (command) health checks, project quotas, a registry allow-list and an AppArmor profile for containers (Planned, no milestone yet). They are refused or missing today.

Added with M5:

Feature Manifest key or command
podos deploy without an image: uploads the source and builds it on the server with BuildKit. See Build from source build; podos daemon --build-timeout, --build-memory, --build-cache-max, --build-context-max, --build-parallel
An install script and a systemd unit for the daemon, with upgrade, rollback and uninstall. See Install script. It needs a published release, and there is none yet install.sh
Checks the install script uses podos setup --check-state, --print-modprobe-blacklist

Added after M5, also on the main branch:

Feature Manifest key or command
Files in containers: config files, key files and templates per environment, mounted read-only. See Files in containers files; podos file set, list, get, unset; podos daemon --files-memory
Web UI on the HTTPS API address: login with a token, first setup in a browser, an overview of the server with its capacity, services and domains per project and environment, and variables and secrets you can set and remove. A binary built without make ui serves a page that says the UI is not built in. See Web UI podos setup --web, --web-ui on|off; podos daemon --web-ui on|off; install.sh -- --web

Not in the web UI yet: deploys, releases, files, tokens, server settings, logs, metrics and running commands in a container. They stay in the CLI.

After version 0.1

Version Theme Content
0.2 Operate More of the web UI (logs and metrics screens, releases, files, tokens and server settings), podos ui, alerts, volume backup and restore to S3 or SFTP, recovery key, GitHub and GitLab deploys
0.3 Options HAProxy ingress driver, built-in registry, app catalog, share between projects, advanced ingress section, users, roles and audit log
0.4 Cluster Several nodes: WireGuard mesh, replicated state inside the podos binary, placement, rescheduling, volume replication
0.5 Cloud Hosted Podos with micro-VM isolation per customer

Plans after 0.1 can change. Container user namespaces (container root mapped to an unprivileged host user) are planned right after the proof of concept.

Plugins and serverless

Planned These are design ideas. None of it is built, and none of it is in the manifest reference.

Plugin system

Capabilities outside the core runtime are meant to be plugins. The plugin contracts come only after the core lifecycle is dependable. Plugins live in a separate repository, podos-org/podos-plugins, not in the core repository.

The first plugin is planned to be Cloudflare support:

Serverless