Container Management

The Containers page lists every container on the host — Docker or Podman, DockPod-managed or not — with:

• Filter tabs: All / Running / Stopped
• Start, stop, restart, remove (with a confirmation dialog on destructive actions)
• Live logs via WebSocket, demuxed from Docker's stdout/stderr stream
• Interactive console via WebSocket — see Console below
• Live CPU/memory stats via WebSocket, polled every 2 seconds
• Auto-refresh — the list polls every 15 seconds, so you don't need to reload the page to see a container someone else started, stopped, or removed

Console

A container's detail page has a Console tab — a full interactive terminal (xterm.js) attached over WebSocket to a docker exec session inside the container (bash if present, falling back to sh), the same mechanism a database's own Console tab uses to drop into psql/mysql/redis-cli/mongosh instead of a raw shell. No network port needs to be exposed for this to work — it goes through the Docker API, not a TCP connection to the container — so it's available on every container regardless of what (if anything) is published to the host.

Container Resources

Pro. From a container's own detail page, Optimize bumps its memory (128–16384MB), CPU (0.1–16 vCPU), and process (64–8192 pids) limits live via the Docker API — no restart, no rebuild. Unlike Git Deployment apps' own Optimize, this works on any container on the host, DockPod-managed or not, and isn't tied to a persisted record: it's a one-off live adjustment for the situation right now (e.g. an emergency vertical-scale during an incident), not a setting that survives a stop-and-recreate. All three fields are pre-filled with the container's current live values, so leaving one untouched resubmits it unchanged rather than resetting it.

Projects View

Containers created by docker compose are automatically grouped by their com.docker.compose.project label under the Projects page — this works for any compose project on the host, not just ones deployed through DockPod. A project's card icon turns green only when every container in it is running.

Status Indicators

Across the app, a green icon means "running" / "online" and grey means "stopped" / "idle" — Dashboard, Containers, Projects, Paste & Deploy, Git Deployments, and Databases all follow the same convention.

Images, Volumes, Networks

Alongside containers:

• Images — list, pull (by reference, e.g. nginx:latest, with a live pull-progress log), remove, prune dangling images
• Volumes — list, remove, prune unused volumes
• Networks — list, remove

All of these poll every 15 seconds as well.