Containers

Use the Containers page to search, inspect, and manage containers on the selected runtime.

Lifecycle

Available actions depend on the container state and runtime. Start, stop, restart, pause, unpause, rename, remove, inspect, logs, terminal, stats, clone, commit, backup, and restore appear where the runtime supports them.

Create

The create dialog builds a container configuration from the selected local image and entered options. Creating a container does not implicitly promise to pull a missing image or start the new container. Pull first when necessary, then start it explicitly.

Review ports, mounts, environment variables, resource limits, restart policy, and network settings before creating. Runtime capability gates may hide options that the selected backend cannot support.

Inspect, clone, and commit

• Inspect shows the runtime's container data.
• Clone copies supported configuration into a new create flow; it does not copy volume data.
• Commit captures the writable container layer as an image and does not include mounted volume data.

Backup and restore

Backup produces a Dockerman archive containing a manifest and the selected container, volume, and bind-mount data. Use the preview before restoring, and review every bind mount because Dockerman does not classify arbitrary host paths as safe.

Restore recreates supported resources from the archive. It does not guarantee that the original runtime networks exist, and the restored container is not automatically documented as started. Review name, ports, volumes, networks, and image availability, then start it explicitly if needed.

Batch actions

Enable the page's batch mode to select multiple rows. Only the actions shown in the current toolbar are supported. Ordinary Ctrl/Cmd+Click and single-letter shortcuts are not documented for batch selection.