Skip to main content

Check that a started stack's containers see their data

POST 
/migrate/containers/:name/check

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}/check"

The data check of step 20: for each bind mount of the stack's containers whose host path is under /mnt/user or /mnt/cache, whether the path exists and is not empty. A directory counts as empty when it holds no entry, a file when it has no byte; a path that cannot be read is unreadable, never ok. It reads one directory entry of each path (which can spin a disk up), when asked and never on a timer, and records that a check ran since the latest start, which confirmMigrationContainer needs. A stack with no bind mount under those paths has nothing to check and is allOk. Refused with 409 container_not_started for a stack that was not started, 409 no_container while the stack has no container (its start has not created one), 409 parity_not_initialized and 404 migrated_stack_not_found as startMigrationContainer does.

Request​

Responses​

What the stack's containers see.