Container Management¶
Qbee deploys and orchestrates containers across your fleet using desired-state configuration. You define which containers should run on which devices, the agent converges to match, and the platform reports inventory and status back. Containers that exit are automatically restarted.
How It Works¶
The agent manages containers as part of its normal convergence cycle. On each poll, it reconciles the running containers against the desired state you committed in the console. If a container is missing or has drifted, the agent recreates or restarts it. Inventory data, including image, status, and uptime, is reported back and visible in the device inventory tab.
Supported Runtimes¶
| Runtime | Guide |
|---|---|
| Docker | Deploy a Docker Container |
| Docker Compose | Deploy a Docker Compose Project |
| Podman | Podman |
For a more advanced scenario combining Docker Compose with secrets and templated configuration files, see Multi-Service Stack with Secrets.
What Next?¶
| I want to... | Go to |
|---|---|
| Deploy a single container | Deploy a Docker Container |
| Deploy a multi-service stack | Deploy a Docker Compose Project |
| Inject secrets into a multi-service stack | Multi-Service Stack with Secrets |
| Use Podman instead of Docker | Podman |
| See container status in the inventory | Inventory |
| Access a running container | Remote Access |