Unraid icon

Unraid

Interact with the Unraid API — manage Docker containers, VMs, array health, disks, notifications, and system metrics

Actions36

Docker → Restart

AI-generated

Summary

Restarts a Docker container on an Unraid server by issuing a stop, waiting 2 seconds, then issuing a start through the Unraid GraphQL API.

Inputs

  • Container ID (required) — Prefixed container ID (e.g. docker:abc123def456). Use Docker > Get Many to find IDs. The source also matches a bare ID, a short ID prefix of 12 or more characters, or a container name when it verifies state after a failed re-fetch.
  • Maximum Control Level — Caps what this node may do. Options are Use Credential Default (the default), Read, Control and Full. It can only narrow the credential's limit, never raise it. Restart needs at least Control, so setting Read here, or on the credential, makes the operation fail.

Output shape

One item per input item: {"id": , "operation": "restart", "success": true}.

The output does not include the container's resulting state. Use Get afterward if you need it. If the stop or start call errors with something other than a "not found after…" message, the node throws. When the API reports that re-fetch error, the node re-lists containers to check the state. It fails if the container is still running after the stop, or is not running after the start. With Continue On Fail enabled, a failed item returns {"error": message}. Items are processed sequentially.

Examples

Example 1: Restart a container after a config change

Resource: Docker, Operation: Restart, Container ID: docker:abc123def456, Maximum Control Level: Use Credential Default (credential must be Control or Full).

Example 2: Let an AI Agent restart containers but nothing destructive

Resource: Docker, Operation: Restart, Container ID set from an expression, Maximum Control Level: Control.

Links

Discussion