Container View
The Container view shows all containers on a device. Use it for day‑to‑day operations, break‑fix, and verification after deployments.
Table and columns
- Columns (typical):
- Name: Container name. Click to open quick actions.
- Image: Tag or digest. Hover to see full reference; click Inspect for digest.
- State/Health: running, exited, restarting; health: healthy, unhealthy, starting.
- CPU/MEM: Live usage where available.
- Ports: Host→Container mappings (e.g., 0.0.0.0:8080→8080/tcp).
- Uptime/Created: How long it has been running or since created.
- Node/Device: Shows the device name.
Common actions
- Start/Stop/Restart: Control lifecycle quickly; use Restart to pick up environment changes applied outside templates.
- Logs: Stream live logs, search logs and navigate seach results.
- Exec/Terminal: Open a shell inside the container with TTY.
- Inspect: View environment, mounts, ports, image digest, health status, and restart policy.
- Recreate/Update: Pull the specified tag/digest and recreate the container preserving volumes and ports.
- Remove: Stop and delete a container (data in named volumes remains unless volumes are removed separately).
Bulk actions
- Select multiple containers to Stop/Start/Restart in bulk.
Advanced options
- Pull policy: Choose to always pull before recreate, or only if missing.
- Restart policy: Set on-failure/always/unless-stopped depending on workload tolerance.
- Resource limits: CPU shares/quotas and memory limits can be inspected; change via Template for consistency.
- Port conflicts: If a requested host port is in use, the action will fail. Change the port variable in the Template and redeploy.
- Image provenance: Prefer digest pins (image@sha256:...) for critical services to ensure exact versions.
Tips
- Use registries with read-only credentials for pulls.
- Prefer Templates for repeatable deployments; use direct container actions for break‑fix tasks.
- After a recreate, verify the running image digest in Inspect to confirm the update.