sandbox_publish_version

Records an image you pushed to the account's registry as a named version of a service, so other boxes can run it without building it again.

sandbox_publish_version records an image you pushed to your account's registry as a named version of a service, so other boxes (or other agents on your team) can run it without rebuilding. sandbox_status.registry gives the server, the repository and the exact imagePrefix (<server>/parallelsandbox/tenant-<account>:); every box of the account is already logged in to that registry, to push and to pull. There is one repository per account, so the image tag carries the service: <imagePrefix>api-a1b2c3d. Boxes are x86_64, so push linux/amd64 images (or multi-architecture ones). image must start with imagePrefix and is not checked for existence, so push first; label is unique per service (reusing one returns 409). sandbox_versions lists them, optionally for one service. Pushing an image is outbound traffic from the box and is metered like any other. The registry has no expiry rule: an image stays until you delete the versions that use it or the account is deleted. DELETE /v1/versions/{id} removes the version record, and also deletes the image when no other version of the account uses the same tag; while another version still uses it, only the record goes and the returned reason names those versions. Pushing a tag again replaces its image; a box's registry login can push and pull but not delete. Another box runs a version by declaring it in services (Run a published version); a worked example is in Team setup. While the box that runs a service is still up, other boxes can also reach it through a link, without an image (Links to other boxes).

Every tool and topic is listed in the tool reference.