Skip to main content

Lima

@jpisgeek/limav2026.11.19.2· MIT· 1d agoBEHAVIORS
01README

One dedicated Linux VM on a Mac, owned and driven through Lima. Renders the whole configuration from pinned inputs instead of inheriting Lima's default template, so the guest gets no host home, no agent or X11 forwarding, no host keys, no proxy environment, and no port that was not listed. Ownership is a marker this model wrote; a VM that merely shares the name is left alone. Drift is reported as replacement-required and never repaired in place, a failed create deletes nothing, and destroy is a separate door that wants the exact name, a stopped VM, and a preservation decision.

02Release Notes

Bound owned limactl timeout/cancellation cleanup: SIGTERM, SIGKILL after 250 ms when needed, cancelled output readers, and child exit before mutation-lock release. Preserve the caller cancellation reason. Retain macOS/architecture, ownership, path and drift guards. This does not roll back VM activity or stop detached descendants; inspect before retrying interrupted mutations. Includes runtime-major Zod alignment and corrected public docs.

03Behaviors1
@jpisgeek/limav2026.11.19.2lima.ts

Global Arguments

ArgumentTypeDescription
namestringLima instance name; also the ownership key
limaHomestringDedicated LIMA_HOME for this instance; never the default ~/.lima
limactlPath?string
limaVersionstringExact approved limactl version, e.g. 2.2.0
arch?enum
vmType?literalv1 supports the Virtualization.framework backend only
cpusnumber
memorystring
diskstring
mounts?array
portForwards?array
provision?arrayReviewed credential-free provisioning scripts; full bodies persist in config artifacts
sshLocalPort?number
startTimeoutSec?number
commandTimeoutSec?number
lockStaleSec?numberDeprecated compatibility input; lock age never permits takeover. OS locks release on process exit.
fn inspect()
Read the host's Lima capabilities and this instance's observed state. Missing, unmanaged, and unreadable are recorded as different facts. Nothing is changed.
fn plan()
Render and validate the complete configuration, hash it, and say what applying it would mean: create, noop, replacement-required, or blocked. No VM is created.
fn create(configHash: string)
Create the exact planned instance without booting it. Requires the reviewed config hash; refuses an existing instance whether owned or not, and never deletes what a failed create left behind.
ArgumentTypeDescription
configHashstringThe plan's configHash, as reviewed
fn start()
Start the owned instance and wait for Lima to report it running. Already running is a no-op.
fn verify()
Check the running guest against the plan: config identity, guest OS and arch, actual mounts, port forwarding policy, SSH settings, and readiness. Each check is recorded separately.
fn stop()
Gracefully stop the owned instance. No force escalation; a stop that fails is reported, not retried harder.
fn destroy(confirmName: string, preservation: enum, backupRef?: string)
Delete the owned, stopped instance and its disk. A separate door: the exact name must be typed, a preservation decision recorded, and the instance freshly inspected. Never a rollback step.
ArgumentTypeDescription
confirmNamestringMust equal the instance name
preservationenumWhy deleting the disk is acceptable
backupRef?stringWhere the verified backup lives; required with backup-verified

Resources

host(infinite)— What the Mac and its limactl offer: version, backend support, the dedicated home, and every unmet prerequisite.
instance(infinite)— Observed state of the one instance this model may own: missing, unmanaged, owned, or unknown, with Lima's own status and sizes.
plan(infinite)— The rendered configuration's hash, the action it implies, the keys that drifted, and what still blocks it.
verification(infinite)— Isolation and identity checks against the running guest, each named with its own pass/fail.

Files

config(application/json)— Complete rendered config including provisioning scripts. Only reviewed credential-free scripts are allowed; retained indefinitely (GC keeps 10 versions).
04Previous Versions1
2026.11.19.1MIT

First public release from preserved Lima work. Hardened VM ownership and isolation, current Swamp schema/identity compatibility, real Lima 2.3.0 inspect and configuration validation. 39 offline tests pass. Guest creation/start/stop/destruction have not been exercised live.

05Stats
A
100 / 100
Downloads
4
Archive size
32.7 KB
  • Has README or module doc2/2earned
  • README has a code example1/1earned
  • README is substantive1/1earned
  • Most symbols documented1/1earned
  • No slow types (deprecated)1/1earned
  • Dependencies pass trust audit2/2earned
  • Docs keep secrets in a vault1/1earned
  • Has description1/1earned
  • Platform support declared (or universal)2/2earned
  • License2/2earned
  • Verified public repository2/2earned
06Platforms
07Labels