Citadel DocsDocker Standalone
Connect one Docker host and manage its containers and Compose applications.
A Docker Standalone Platform connects to one Docker engine. Use it for Deployments and Compose Stacks. For cluster scheduling, use a Docker Swarm Platform.
Add a Platform
- Open Platforms and select Add Platform.
- Choose Docker Standalone.
- Choose Local, Agent, or Edge Agent for the connection.
- Enter the connection settings and save the Platform.
- For Edge Agent connections, run the generated enrollment command on the Docker host.
- Open the Platform when it comes online to see its Docker resources.
For a Local connection, Core needs access to the host's Docker socket. For a remote connection, follow Agent setup or Edge Agent setup.
Explore Docker resources
| Page | Common tasks |
|---|---|
| Containers | Read logs, inspect configuration, open a terminal, and manage state |
| Images | Pull an image and inspect its layers and container usage |
| Networks | Create networks and inspect attached containers |
| Volumes | Create storage, browse files, and download contents |
Your permissions and the Platform connection determine which actions are available.
Existing Docker resources can be visible before they are managed as Citadel Deployments or Stacks. Use adoption when you want Citadel to manage an existing application's configuration.
Deploy applications
- Use a Deployment for one container.
- Use a Web Editor Stack for Compose content stored in Citadel.
- Use a Git Stack for Compose files stored in a repository.
For metrics and connection failures, see Platform monitoring and troubleshooting.
Platform statistics
The Stats tab shows container CPU and memory usage, Docker storage filesystem capacity, Network Usage, and Disk I/O. Network and disk I/O offer Accumulated bytes and Throughput in bytes per second. Their summary totals cover the selected period in either view. Both default to Accumulated and remember your selection separately in your browser's localStorage, shared with container statistics.
Traffic is calculated from changes in each container's counters before adding containers together. Restarting, replacing, or removing a container does not subtract already recorded traffic. These charts measure containers, not all network interfaces or all disk activity on the host. Disk I/O differs from Disk Usage, which measures filesystem capacity.
At least two observations of a container are needed to measure traffic. Missing block-I/O counters remain unavailable. Older platform samples that do not contain individual container counters cannot supply these totals or rates; new samples populate the charts. Unobserved activity before a counter reset cannot be recovered.