Skip to main content

VCON Build & Run

Build VCON containers and execute them on the bytecode / VM path. This page is only about morph vcon …, not about the default morph run native flow.

Building​

morph vcon build

Produces or updates a .vcon artifact for the current project according to your [vcon] (and related) settings in morph.toml. Output location and naming follow the toolchain implementation for your version.

Running (VCON)​

morph vcon run

Builds if needed and runs the container on the VCON / VM execution path (not the same as launching the native .exe from morph run).

Native morph run (not VCON)​

morph run

For a normal application project, morph run drives the LLVM → native executable pipeline and then executes that binary (see runRunCommand in the CLI sources). It is not an alias for morph vcon run.

If you need both in the same session, treat them as different targets and document which artifact you are testing.

Build output (illustrative)​

Layout varies by version; you may see something like:

build/
├── …                    # native dev artifacts when using morph build/run
├── …/*.vcon             # container when using morph vcon build
└── .morph_cache/        # caches (tensor/codegen/etc., project-dependent)

Configuration​

Enable and tune VCON in morph.toml with [vcon] and nested sections such as [vcon.permissions], [vcon.resources], [vcon.pack], etc. The project generator does not emit [vcon] by default; add it when you adopt the container workflow. See Project morph.toml reference.

Next steps​