Skip to content

Latest commit

 

History

History
39 lines (32 loc) · 1.58 KB

File metadata and controls

39 lines (32 loc) · 1.58 KB

Containers

The perry/container and perry/compose modules manage OCI containers and multi-container stacks directly from Perry programs — same model as docker compose up, but with the spec as a TS object literal and the orchestration engine running natively in-process (no shell-out to docker-compose).

For the full container subsystem documentation see the dedicated Containers section:

  • Overview — module layout, backend auto-detection, and the canonical lifecycle pattern.
  • Single-Container Lifecycleperry/container: run, inspect, logs, exec, image management.
  • Compose Orchestrationperry/compose: up, down, ps, healthcheck-gated depends_on, env-var interpolation.
  • Networking — internal-only networks, port maps, and the cross-service-DNS workaround.
  • Volumes — named vs. bind mounts and preservation semantics on down().
  • Security — capability isolation, cosign image verification, workload-graph policy tiers.
  • Production Patterns — full Forgejo deployment case study with the patterns it surfaced.

Quick start

{{#include ../../examples/stdlib/container/snippets.ts:compose-up-simple}}
{{#include ../../examples/stdlib/container/snippets.ts:compose-down}}

See the linked pages above for the full API surface, production patterns, and case studies.