Actions36
- Array Actions
- Disk Actions
- Docker Actions
- Notification Actions
- System Actions
- VM Actions
Docker → Start
AI-generatedSummary
Starts a Docker container on an Unraid server by ID via the Unraid GraphQL API, and returns the container's resulting state. Requires at least the "control" level.
Inputs
- Container ID (required) — Prefixed container ID (e.g. docker:abc123). Per the source, it also matches a bare 64-char ID, a short ID prefix of 12+ characters, or the container name. These alternate forms are only used for the fallback state check. The start mutation itself receives the value as entered, so the full prefixed ID is safest. Use Docker > Get Many to find IDs.
- Maximum Control Level — Caps what this node may do (credential default, read, control, full). It can only narrow the credential's limit, never raise it. Start needs an effective level of control or full, otherwise the node errors before contacting the server.
Output shape
One item per input item, containing the container's id, names, state and status after the start call.
Unraid's mutation can error with "not found after starting" even when it succeeded. In that case the node re-lists containers and checks that the state is RUNNING. If it isn't, it throws an error with the current state. If the container is running but missing from the list, it returns {id, operation, success, state}. Other API errors are thrown, or emitted as {error} items when Continue On Fail is enabled.
Examples
Example 1: Bring a container back up after a maintenance window
Resource: Docker, Operation: Start, Container ID: docker:abc123def456
Example 2: Start containers found by an earlier Get Many step
Container ID set to the expression {{ $json.id }}, with the credential's control level at Control or higher