Podos A lightweight container platform Early development · not released

Operations

Limits of this version

This page lists what Podos does not do, as of the code on the main branch (milestones M0 to M5). There are still no release binaries: you build podos from source, or, Available once a release exists, use the install script. The same list is printed by:

podos version --limits

If you upgrade a server that was set up with an M2 build, see Upgrading from an M2 server.

Runtime

Limit Planned fix
Available Podos needs Linux 5.6 or newer, systemd 245 or newer, cgroup v2, crun, conmon and nft.
Available A service without resources.memory gets 512 MiB, with no swap beyond it. A process that goes over it is killed by the kernel and shown as oom-killed. Set resources.memory for databases, JVMs and build steps.
Available Containers can use TCP and UDP over IPv4 (and ping), Unix sockets, and the routing netlink to list interfaces. Packet capture, DHCP clients, raw sockets, other netlink protocols, SCTP, AF_ALG, vsock and Bluetooth are not available. IPv6 inside application networks is off.
Available The seccomp profile covers only the 64-bit architecture of the server. 32-bit x86 images do not run on x86_64 servers. On arm64 servers, 32-bit ARM images are allowed.
Available Volumes belong to one environment and are bind-mounted from the server's data directory. Removing a service or environment never deletes volume data unless you ask for it. volume backup Planned · 0.2
Available Files are at most 1 MiB each, 64 per environment and 16 per service, mounted read-only at one path each. No directory of files, no file from the repository, no file inside a volume or over /etc/hosts, /etc/hostname or /etc/resolv.conf. A change takes effect at the next deploy, not in running containers. See Files.
The disk space a container writes is not limited per container. Available Podos refuses to create containers when the data disk has less than 1 GiB or 5% of inodes free.
Available Logs keep roughly the last 10 MiB per container. Each container has one log file of at most 10 MiB. At the limit the file starts empty and older lines are lost. The size is not configurable. persistent logs and metrics Planned · 0.2
Containers run as host root, without user namespaces, with a reduced capability set, a seccomp profile and no-new-privileges. user namespaces after 0.1
Services must keep running or be restarted by their restart policy; run-to-completion jobs are not supported. not yet scheduled
Available Health checks are http or tcp. Exec (command) checks are refused. Planned
Available build needs BuildKit and crun 1.15 or newer on the server; the install script provides both. Without them a release with build is refused.
Images are pulled anonymously; no private registries. not yet scheduled
No namespace quotas and no registry allow-list. Planned

Node protection

Available At every start the daemon reads the server's memory, CPU count and disk, because servers get resized. Then:

Files

Available What files in containers limit:

What Limit
One file, also a template once rendered 1 MiB
Files in one environment 64
Files mounted by one service 16
Different values in one template 256
Stored content of a namespace, including what old releases still pin 256 MiB
file set and file unset per token 60 per minute

A template is rendered when a container is created, with the values the environment holds then, so a restart or a rollback uses today's values.

Files memory

Plain files are written to the data disk with the container's other state. Secret files, and templates that hold a secret once rendered, are written only to a memory file system of the daemon, never to the data disk.

Builds on the server

Available What build does and does not do. See Build from source for the details.

Access

Limit Planned fix
The CLI works only on the server, as root, over the Unix socket. Available HTTPS API, tokens, podos login, contexts
One server only. Planned · 0.4 several nodes
Available The web UI shows the server, services, domains, variables and secrets, and changes variables and secrets. Deploys, releases, files, tokens, server settings, logs and running commands are CLI only. A binary built without make ui has no UI. logs and metrics screens Planned · 0.2
Available The install script and its systemd unit are built, but there is no published release to install from yet. Install from a source build today. the first release

Remote access

Available These limits apply to the remote access over HTTPS:

Limit Planned fix
No CA rotation: the internal CA cannot be replaced yet. not yet scheduled
HTTP proxies are not supported for server connections; proxy variables are ignored. not yet scheduled
A server upgraded from M2 has no admin token. Create one as root on the server with podos token create --name NAME --kind admin.
A deploy token can read its environment's secrets through the containers it deploys.
Several servers are separate: no hub, no combined view. Planned · 0.2 podos ui

Networking, restarts and rollouts

Available These are the facts behind the limits above.

Upgrading from an M2 server

An M2 build ran containers with only a loopback network, no restart, did not act on port, domains, tls, publish and health, and refused volumes. All of that is now in place. A server set up with M2 needs nftables and has no admin token; see Upgrading an M2 server. Available Containers started by a version before M3 keep running after an upgrade but without networking until the application is deployed again.

Validation limits

What Limit
Manifest file 256 KiB
Services per manifest 200
Environments per manifest 20
Replicas per service 1000
env entries per service 1000
env value 32 KiB
podos logs --tail 10000 lines per replica
Concurrent log streams 64 per daemon, 8 per environment