Skip to main content

What the migration's Phase D can create, and what it has created

GET 
/migrate/containers

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

Example request
curl --request GET \
  --header "Authorization: Bearer $HOSERVA_TOKEN" \
  "https://$HOSERVA_HOST:8008/api/v1/migrate/containers"

Phase D's container steps as data, from the latest scan. templates are every template of the scan grouped by class in the order the groups are shown (autostart in Unraid's own autostart order, then running, stopped, template_only and unknown); only a creatable template on Unraid's autostart list whose stack does not exist yet is preselected, so with no capture (class unknown) nothing is. Every one can still be selected. composeProjects are the Compose Manager projects, offered with their own compose.yaml; byHand are the containers created with docker run and their image, which nothing is generated for: they are recreated by hand. The preview of each (the generated Compose, every warning including the writable-layer warning) is getMigrationTemplate, and should be read before createMigrationStacks. stacks are the stacks createMigrationStacks created, in the order they are offered for starting (Unraid's autostart order first), each with its state; awaiting names the started stack that must be confirmed or stopped before another is started, and next the first stack not started yet; a stack that was started, stopped and never confirmed is offered as next only when none of those is left. parityInitialized is false until the migration is past its point of no return (initializeMigrationParity); the operations that create or start something refuse until then. This reads no disk. 404 no_migration_report before a scan has finished and 404 no_template_preview for a report made before scans converted templates.

Responses​

The offer.