reactor model publish

reactor model publish [<name>:<release>] [flags]

Description

Publish a model release by building and pushing its image and optionally uploading weights. Use reactor model deploy to deploy the published release. Workspace-aware: When run from a workspace (any directory under one containing a reactor.yaml, stopping at the enclosing repository root) with no positional argument, the model name and release tag are taken from the file’s model.name and model.version fields, so you can simply type reactor model publish. An explicit <name>:<release> on the command line can override the workspace release tag, but its <name> part must match the workspace model.name or the command is rejected. Image source: The image is built from reactor.yaml’s build: block, with the Dockerfile generated in memory and never written to the workspace. A Dockerfile on disk takes the build over: the workspace ./Dockerfile is built verbatim when it exists, -f/--dockerfile builds an explicit path, and either way reactor.yaml’s build fields are ignored with a stderr note naming them. --no-dockerfile builds from reactor.yaml even when a ./Dockerfile exists, and is mutually exclusive with -f. --source skips the build entirely and loads an existing image. --build-secret supplies a build secret (id=<id>,env=<var> grammar - see reactor build --help); required whenever the Dockerfile (on-disk or generated) declares a secret mount, such as a build.run hook with one. Ignored with --source. --build-env overrides a build.build_env value for this build, with the same grammar and rules as reactor build --help. Repeatable; a bare KEY takes its value from the environment. Ignored with --source. Weights:

--weights <path>: Upload weights from this file or directory for this release, or pin an hf://org/repo[@rev] reference and finalize its hub-file manifest; no weight bytes are uploaded. Without it, falls back to the workspace’s runtime.weights_path when reactor.yaml declares one; with neither, the weights step is skipped and reactor model deploy reuses the previously deployed release’s weights (upload new ones later with reactor weights upload if they changed).
--no-weights: Skip the weights step even when reactor.yaml declares runtime.weights_path - for a machine that holds no weights, such as a CI agent publishing the image alone. Mutually exclusive with --weights.
--force: Re-upload weights even when the target release already has a matching bundle on the server (only meaningful with --weights).

Examples:

reactor model publish                            # workspace: read name+version from reactor.yaml
reactor model publish my-model:v1.0.0-gabc1234
reactor model publish my-model:v1.0.0 --source my-org/my-image:v1.0.0
reactor model publish my-model:v1.0.0 -f infra/Dockerfile.runtime
reactor model publish my-model:v1.0.0 --no-dockerfile # ignore the on-disk ./Dockerfile
reactor model publish my-model:v1.0.0 --weights ./checkpoints/
reactor model publish my-model:v1.0.0 --weights ./checkpoints/ --force
reactor model publish --source my-org/my-image:v1.0.0 --no-weights # CI: image only
reactor model publish my-model:v1.0.0 --dry-run

Options

Flag	Description
`--build-env stringArray`	Override a build.build_env value for this build, KEY=VALUE (repeatable; a bare KEY takes its value from the environment). Ignored with `--source`.
`--build-secret stringArray`	Build secret, id=<id>,env=<var>\|src=<path> (repeatable; e.g. id=github_token,env=GITHUB_TOKEN). Ignored with `--source`.
`-f, --dockerfile string`	Path to an explicit Dockerfile (relative to the build context = cwd); defaults to the workspace ./Dockerfile when one exists
`--dry-run`	Print the resolved plan and exit; no side effects
`--force`	Re-upload weights even when the target release already has a matching bundle on the server
`--no-dockerfile`	Build from reactor.yaml, ignoring an on-disk Dockerfile
`--no-register`	Fail if the model is not already registered, instead of auto-creating it from the workspace reactor.yaml (publish registers on miss by default)
`--no-weights`	Skip the weights step even when reactor.yaml declares runtime.weights_path; deploy reuses the previously deployed release’s weights
`--platform string`	Target build platform (default linux/amd64). Overrides build.platform in reactor.yaml; an explicit ‘FROM `--platform`=’ in the Dockerfile still wins for that stage. Ignored with `--source`.
`--source string`	Use an existing image reference instead of building from a Dockerfile
`--weights string`	Weights source for this release: a local file or directory to upload, or an hf://org/repo[@rev] reference pinned and finalized as a hub-file manifest, with no upload (omit to use the workspace’s runtime.weights_path when declared, else reuse the previously deployed release’s weights at deploy time)
`--workers int`	Parallel workers for bundle hashing and per-file uploads during the weights step (default 4)

Global options

Flag	Description
`--server string`	Reactor API server URL (default “https://api.reactor.inc”)
`-v, --verbose`	Enable verbose output

Get Started

CLI & Platform

Build a Model

Media & Transport

Releases

reactor model publish

Description

Options

Global options

See also

​Description

​Options

​Global options

​See also

Description

Options

Global options

See also