Container Management FAQ¶
How do I pull images from a private registry?¶
Open the Registry Authentication tab under Docker (or Podman), enter the registry hostname, username, and password, then click Save settings and Commit changes. In the container definition, prefix the image name with the registry hostname.
For example, an image my-image:latest hosted at my.private-registry.com must be defined as:
my.private-registry.com/my-image:latest
What happens when a container exits?¶
The agent restarts it automatically on the next convergence cycle. There is no need to intervene unless the container is exiting due to a configuration error, in which case it will continue to restart and fail until the configuration is corrected.
Where do I see container status?¶
Running containers appear in the device inventory tab under Docker (or Podman), with status, image, uptime, and action buttons for viewing logs and opening a shell. See Inventory for details.
Can I build images on the device?¶
The Docker Compose integration supports a build context field, but building on the device is not recommended for production. Use immutable image tags and pre-built images from a registry for predictability and consistency.
What are the Docker Compose optional fields?¶
The Docker Compose integration accepts the following optional fields on each project:
| Field | Description |
|---|---|
| Clean | Remove any Compose projects previously deployed by Qbee that are no longer in the configuration |
| Pre-condition | (Optional) A command or script that must return exit code 0 before the Compose configuration is evaluated |
| Template parameters | Values to substitute into a templated compose file |
| Skip restart | Do not restart the project when a container has exited |
| Build context | A build context for the project (development use only; not recommended for production) |