The platform’s managed base image, paired with the Dockerfile FROM it goes with.
One value rather than two loose strings, because the two must agree and used to be able
to disagree: the Python client’s default named the managed base for baseImageArn while
its Dockerfile hardcoded an unrelated registry literal in its FROM, so changing either
left the other pointing somewhere else.
#[napi(object)] is acceptable here where it is not for a guarded type: the pairing is the
point and both halves are required fields, so a structurally-valid object is a valid
pairing. workingDir is what docker inspect reports for WorkingDir, and empty means
the image declares none — a field because a caller with a purpose-built image is the only
one who can say what theirs declares.
Properties
Section titled “Properties”dockerRef
Section titled “dockerRef”dockerRef: string;name: string;workingDir?
Section titled “workingDir?”optional workingDir?: string;Default Value
Section titled “Default Value”""Provenance
Section titled “Provenance”This page is generated from bindings/microvms-js/index.d.ts by TypeDoc 0.28.20 and typedoc-plugin-markdown 4.13.1, run from site/scripts/gen-reference.mjs on every pnpm run sync, so an edit made here is overwritten by the next run.
To change the page, change the doc comment in the binding’s Rust source, then regenerate the declarations with mise run dts. mise run dts:check fails when the committed file no longer matches the source.