Docker Compose resource budgets for small AI services

Compose is a contract with your future self

docker-compose.yml encodes ports, volumes, environment variables, and restart policies in one place. That contract becomes invaluable when you return to a project after months or hand it to a housemate who just wants “the AI thing” to work. The cost is overhead: the Docker engine, image pulls, and sometimes sluggish I/O on SD cards.

Choose Compose when you run multiple cooperating services—assistant, reverse proxy, metrics exporter—or when you want identical dev and prod trees. Skip it when a single static binary plus systemd is objectively simpler.

Memory and CPU limits that reflect reality

Use mem_limit or deploy.resources.limits in modern Compose formats to cap containers. Without limits, a memory leak in a sidecar can take the host down. Set limits slightly above steady-state RSS you measured, not wishful thinking.

CPU shares and quotas prevent noisy neighbours when sharing a NAS or shared VPS. Test builds on the slowest hardware you support; laptops lie.

Health checks and restart storms

healthcheck directives let Compose restart unhealthy containers automatically. Tune interval and retries so transient model outages do not flap endlessly. Expose a lightweight /health endpoint in your stack or probe a static TCP port the assistant listens on.

Logs during restart storms are noisy; aggregate them externally if you need trends. Sometimes lowering restart aggressiveness surfaces the real root cause faster.

Volumes: config secrets and state

Bind-mount config directories for quick edits, but restrict permissions on the host. Named volumes help portability but obscure file locations—document them. Never bake API keys into images; inject via env files excluded from git.

State includes conversation transcripts, cursor files for cron jobs, and downloaded attachments. Decide retention policies; GDPR and common sense both dislike infinite undeleted personal data.

Logging drivers and disk space

json-file driver defaults can fill disks on chatty assistants. Set max-size and max-file rotation. Alternatively ship to journald or a remote collector. Test log volume under peak webhook load, not idle chatter.

If you run on ZFS or btrfs, snapshots help recovery but do not replace monitoring free space proactively.

Integration with PicoClaw guides

PicoClaw’s Docker and Compose guides sketch patterns for keeping containers small and configs explicit. Treat them as templates: adapt networks, hostnames, and secrets to your environment.

Revisit images quarterly for security patches. Lightweight assistants reduce churn, but base images still age.

Operational wrap-up: shipping without regret

When you operationalize the ideas behind “Docker Compose resource budgets for small AI services,” start with a single toggle—an environment flag, a config stanza, or a feature branch deploy—that lets you compare old and new behaviour side by side. Use staging hardware you can afford to break: a spare Raspberry Pi, an old laptop, or a tiny cloud VM. Measure resident set size, cold-start time, p95 latency to your LLM provider, and error counts from journald or container logs before you point production webhooks at the stack. Week-one reviews usually surface missing timeouts, naive retry loops, and logging that omits request IDs; week-four reviews catch slow leaks, SD card exhaustion, and TLS renewal gaps. Write rollback steps next to rollout steps: which systemd unit to restore, which container tag to pin, which API key to rotate if a webhook secret leaks. Reliability is the product feature nobody applauds until it disappears.

Documentation debt kills homelab automation faster than clever bugs. For slug “docker-compose-resource-budgets,” keep a one-page runbook: ASCII diagram of data flow, listening ports, file paths for configs, and where secrets live on disk. Note the exact PicoClaw or companion binary version you deployed and link to upstream release notes. When vendors deprecate endpoints or models, you diff your runbook against official docs instead of archaeology on live systems. If anyone else—family, teammates—might restart services, document safe stop/start order and how to verify health. The goal is that a tired operator at midnight can follow steps without reading the entire blog archive.

Treat cost and reliability as one system: log every LLM call with approximate token counts, bucketed by workflow, and compare against invoices weekly. Spike detection should trigger investigation before budgets hard-fail—often a runaway cron or a duplicated webhook is the culprit, not “the model got smarter.” Pair financial telemetry with synthetic probes: a canary prompt that runs hourly and asserts latency and format constraints. When probes fail, page or notify through the same Telegram or Discord channels your humans already watch so anomalies do not live only in Grafana. This closing loop—money, latency, correctness—is how lightweight assistants remain boring infrastructure instead of science fair exhibits.

Where to go next in the PicoClaw knowledge base

This site’s guides translate patterns into commands: Raspberry Pi and Pi 5 setups, self-hosted assistants, Docker and Compose, systemd services, nginx HTTPS, Cloudflare Tunnel, Tailscale, n8n webhooks, Linux cron jobs, Telegram and Discord bots, and local models via Ollama or OpenAI-compatible gateways. The providers and configuration pages list how to wire OpenAI, Anthropic, Gemini, Groq, DeepSeek, OpenRouter, and more without scattering secrets across shells. Security, workspace, heartbeat, and API references explain sandboxing, scheduled prompts, and HTTP integration in depth—use them when you promote experiments to always-on services.

Comparison and alternatives articles situate lightweight Go agents next to heavier Python or Node stacks so you pick runtime deliberately, not by default. News and community links track upstream changes. If you are uncertain, ship the smallest vertical slice: one scheduled summary, one chat command, or one signed webhook—prove observability and cost discipline before layering complexity. Edge constraints on RAM, thermals, and bandwidth are not temporary hurdles; they define the niche where small binaries and clear policies outperform monolithic demos that never leave a developer laptop.

Finally, revisit this article—“Docker Compose resource budgets for small AI services”—after your first production month. Annotate what aged poorly: a provider price change, a deprecated API field, a Pi firmware quirk. Update your internal notes and, if you maintain a public fork or gist, refresh it too. The niche moves quickly; static knowledge rots. PicoClaw’s model is to stay small at the edge while models and prices churn in the cloud—your documentation should echo that split: stable operational procedures on the left, volatile model cards on the right. Close the loop with metrics: dollars spent, incidents avoided, minutes saved. Those numbers justify the next iteration of your assistant better than any manifesto.

Accessibility and clarity matter even for personal bots: use descriptive command names, consistent help text, and error messages that suggest the next corrective action. Internationalization may not be your day-one priority, but encoding and emoji handling in chat bridges trips many newcomers—test with non-ASCII samples early. Backups of configuration and prompt templates belong in the same lifecycle as code: versioned, reviewed, restorable. These habits compound; they are how assistants remain maintainable when you are not the only operator anymore.

Performance tuning is iterative: profile before optimizing, and optimize the bottleneck you measured—not the framework you dislike. Network RTT to LLM endpoints often dominates; caching embeddings or deterministic template fragments locally can shave recurring costs. CPU spikes on Pis may be thermal or power-supply sag; rule those out before rewriting code. When you change models, re-benchmark end-to-end latency and weekly spend; a “smarter” model that doubles latency can break chat UX even if quality improves. Keep a changelog of model IDs and prompt hashes so regressions are bisectable instead of mysterious.