Skip to main content

Start one migrated stack

POST 
/migrate/containers/:name/start

Required role: admin. Only an account or token with the admin role can call this operation.

Example request
curl --request POST \
  --header "Authorization: Bearer $HOSERVA_TOKEN" \
  "https://$HOSERVA_HOST:8008/api/v1/migrate/containers/{name}/start"

Step 20 of the migration: queues the stack_start job (startStack) for a stack createMigrationStacks created, and records that it was started: the start is recorded before the job is queued, so a start that cannot be recorded queues nothing, and a start that is queued and whose job is then not recorded leaves the stack recorded as started with no job. Containers are started one at a time: this is refused with 409 container_unconfirmed while another migrated stack that was started is neither confirmed (confirmMigrationContainer) nor stopped, which includes one whose start job is still running or whose containers are running, and one recorded as started with no job. When the state of another started stack cannot be read (its start job or its containers), nothing is queued and the read failure is returned as it is, not as container_unconfirmed: 503 docker_unavailable when the Docker Engine cannot be reached, 500 otherwise. A failure to record the start is a 500. Refused before anything is queued with 409 parity_not_initialized until the migration is past its point of no return, 404 migrated_stack_not_found for a name the migration did not create, 409 container_confirmed for a stack already confirmed, 404 stack_not_found when the stack was removed since, and 409 array_stopped or 503 array_state_unknown as startStack answers. The stack's waitSeconds is what Unraid's autostart list waited after starting it, as a suggestion. Run checkMigrationContainer once the job has succeeded.

Request​

Responses​

The queued stack_start job.