Skip to content
HyperOptimizerHyperOptimizerHyperOptimizer Docs

Container requirements

HyperOptimizer can run any container that follows the trial contract. Keep images repeatable, observable, and safe to run in parallel.

Required

Section titled “Required”
  • Required The image is published to your org Images registry (or allowed as custom Docker on Enterprise).
  • Required The image can be pulled by HyperOptimizer for your organization.
  • Required The default command or configured command starts the trial.
  • Required The command accepts managed CLI arguments (--hpo-* by default).
  • Required The process exits when the trial is done.
  • Required Successful trials print at least one valid metric line for each configured objective.
Section titled “Recommended”

Pin dependencies

Reproducibility matters when comparing trials over time.

Log clearly

Print enough context to diagnose bad data, bad arguments, and runtime failures.

Avoid shared writes

Parallel containers should not overwrite the same external path. Prefer paths that include HYPEROPTIMIZER_TRIAL_ID.

Runtime behavior

Section titled “Runtime behavior”

The container should treat each trial as isolated. If a parameter set is invalid, either exit with a clear error or emit a penalty metric that your objective can rank appropriately.