Skip to content

Disable Firecracker and SSH permanently while retaining adapters - #577

Merged
yifanxuaaa merged 1 commit into
layerfs_v2_0_0from
fix/disable-firecracker-ssh
Nov 5, 2026
Merged

yifanxuaaa merged 1 commit into
layerfs_v2_0_0from
fix/disable-firecracker-ssh

Conversation

@yifanxuaaa

@yifanxuaaa yifanxuaaa commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

Firecracker and SSH are permanently unavailable for new LayerFS work on every host, while their adapter implementations and existing resources remain intact. A shared policy supplies the same refusal to discovery, machine setup and CLI/Node/Python dispatch, including builds without machine adapters. Saved workers and forwarded daemons cannot bypass it.

Closes Ephemeral-AI-Lab/layerfs-project#7.

Existing machine records, data and running workloads are preserved. Read-only inspection and explicit cleanup remain available; disabled-machine inspection shows recorded state without probing or starting it. New transfers also refuse before retiring a historical copy on a disabled machine. No runtime override is provided. Native, Docker, Lima, Apple Container and microsandbox retain their support; Lima's SSH transport remains usable.

Support JSON, CLI help, generated SDK declarations, import-env, doctor guidance and active documentation are updated. Re-enablement requires an explicit owner decision and source change. The Firecracker and SSH adapter directories are unchanged, and no files or tests were deleted. Eight historical launch/connection qualification tests remain compiled but ignored with the policy reason; current refusal coverage replaces their product-availability role.

Validation on macOS ARM64, Rust 1.85.1, locked offline private-worktree builds:

  • Shared 27-selection refusal matrix per platform through Rust API, CLI, Node and Python: fixed Unsupported reasons, unchanged record bytes and no worker/daemon connections.
  • Machine coverage: 78 passing cases across retained covering runs; 8 historical cases ignored. Support table checks all named hosts plus Other and both Store kinds; enabled backend/kernel paths and teardown remain covered.
  • Selected API: 36 passing cases; 3 policy cases also pass without the machine feature. CLI: 22 pass. Doctor: 4 pass.
  • Node: 25 pass, 1 daemon-dependent skip. Python: 39 pass, 1 daemon-dependent skip, including strict mypy samples. Generated declarations match the call table.
  • Clippy with warnings denied across all targets of the seven relevant crates; Rust formatting; product boundary guard; 169 tooling tests; changed documentation link targets.

Live Linux/Windows VM qualification and successful live transfer runs are not claimed. The initial transfer selection is native ↔ Docker/Lima/Apple Container (six directions), plus Docker → native → Lima. Firecracker/SSH get refusal checks; microsandbox remains supported outside that initial selection. Durable execution was NOT_RUN, disabled by owner.

Implementation and retained evidence records commands, limitations, ignored cases and the diagnosed development failures. Restriction contract documents existing-resource handling and explicit re-enablement.

Production LOC: 137322 -> 137478 (delta +156). Same tools/production_loc.py counter (blob 31b3cc2baa744d3b525722879e7dc9c2eedd0773) over exact first-parent and staged snapshots exported with git archive. Scope includes first-party Rust/runtime SQL/published JS/Python and handwritten stubs; excludes tests, tools, docs, generated stubs and third-party code. Reference absent (retired R9c; last counted 65,417 at tree 498dd1917812).

…ing adapters

Apply one shared product policy to support data, readiness, machine setup
and public dispatch, including builds without machine adapters. Refuse
new work through saved workers and forwarded daemons before effects;
check transfer leftovers before recovery can retire a disabled copy.
Preserve records, existing workloads, read-only inspection and explicit
cleanup. Update discovery/help, setup and operator documentation.

Refs Ephemeral-AI-Lab/layerfs-project#7.

Validation: machine coverage 78 passing cases, 8 retained historical
qualification tests ignored; selected API 36 passes plus 3 no-machine
policy passes; CLI 22; Node 25 plus 1 daemon skip; Python 39 plus 1 daemon
skip (mypy included); doctor 4; tooling 169. Clippy all targets on the
seven relevant crates, formatting, support/declaration drift and product
boundary checks passed. Live transfer/VM qualification not claimed.
Durable NOT_RUN: disabled by owner. No tests or adapter code deleted.
Ignored test names, retained failures and evidence paths are recorded in
core/docs/issues/project-7/IMPLEMENTATION.md.

Production LOC: 137322 -> 137478 (delta +156)
Scope: first-party core/engine/connect/API Rust, runtime SQL, published JS,
Python implementation and handwritten stubs. Tests, tools, docs, generated
stubs and third-party code excluded. Same counter for exact first-parent
and staged trees: tools/production_loc.py blob
31b3cc2.
Method: git archive <tree> into an empty directory, then
python3 tools/production_loc.py --root <exported-tree> --json.
Reference absent (retired R9c; last counted 65,417 at tree 498dd19).
@yifanxuaaa
yifanxuaaa merged commit b919f50 into layerfs_v2_0_0 Nov 5, 2026
3 of 4 checks passed
Mola-maker pushed a commit that referenced this pull request Nov 6, 2026
…t report

The report said both platforms stayed selectable. That held for the tree the
artifacts were built from (d430474 plus four PRs) but not for the current
base, which contains the policy of layerfs-project#7 (b919f50, #577).
Replace the section with what a command built from the current base does
(not ready, Unsupported before any effect), drop the gap, and state in the
Source row that the artifacts predate that upstream change.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Mola-maker pushed a commit that referenced this pull request Nov 6, 2026
The report called them still selectable, quoting artifacts built before the
policy of layerfs-project#7 (b919f50, #577) landed. On a command built from
this base both are not ready and machine create / connect answer Unsupported
before any effect. Turn the row into a resolved fact and take it off the
open list.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Mola-maker pushed a commit that referenced this pull request Nov 6, 2026
The first run used artifacts built before #577 and later upstream changes.
Rebuild the default and PostgreSQL artifacts from the current base and record
the identity, hashes and results: Node 24 and 22, Python 3.10 to 3.14, the
command alone, the Firecracker/SSH policy on the installed command, and the
PostgreSQL and default builds against a port nothing listens on. The real
PostgreSQL server run could not be repeated because the Docker engine did
not answer; say so. The older sections stay as history.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Mola-maker pushed a commit that referenced this pull request Nov 7, 2026
…t report

The report said both platforms stayed selectable. That held for the tree the
artifacts were built from (d430474 plus four PRs) but not for the current
base, which contains the policy of layerfs-project#7 (b919f50, #577).
Replace the section with what a command built from the current base does
(not ready, Unsupported before any effect), drop the gap, and state in the
Source row that the artifacts predate that upstream change.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Mola-maker pushed a commit that referenced this pull request Nov 7, 2026
The first run used artifacts built before #577 and later upstream changes.
Rebuild the default and PostgreSQL artifacts from the current base and record
the identity, hashes and results: Node 24 and 22, Python 3.10 to 3.14, the
command alone, the Firecracker/SSH policy on the installed command, and the
PostgreSQL and default builds against a port nothing listens on. The real
PostgreSQL server run could not be repeated because the Docker engine did
not answer; say so. The older sections stay as history.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Mola-maker added a commit that referenced this pull request Nov 7, 2026
…SQL/TLS build; pack guard (#589)

* feat(api): let build-native.mjs enable the PostgreSQL and TLS features

The addon build script accepted only --debug, so an addon with PostgreSQL
Stores or https buckets could not be built through it. It now takes an
explicit opt-in list, `--features postgresql,tls`, and passes it on to
`cargo build -p layerfs-node`. Only those two names are accepted; with no
flag the build is unchanged (no features), and anything else is still the
usage error.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* fix(node): make npm pack refuse a package without its addon

`files` lists layerfs.node, and npm silently leaves a listed file out when it
does not exist: packing without a prior `build:native` gave a tarball of 7
files, exit 0, that cannot load. A prepack script now stops with a message
naming the build command.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* docs(api): state how to package and install the three artifacts

Every documented command was run from a checkout; none said how to get the
Node tarball, the wheel or the command onto another machine. api/README.md
now has the pack and install steps for each, the opt-in PostgreSQL/TLS
builds and what they need (OpenSSL headers, patchelf), and that `npm pack`
refuses without the addon. The Python guide says `maturin build` is a debug
wheel. Also corrected: the stale `engine/crates/layerfs-python` path, the
"Linux wheels NOT_RUN" claims now that a Linux x64 wheel was built and
installed, and the doctor test command, whose cold build overruns the 100 s
limit unless built first with --no-run.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* docs(general): record the 2.0.0 artifact qualification on Linux x64

Pins the source, toolchain, sha256 and contents of the Node tarball, the
Python wheel and the layerfs command (release profile, default and
PostgreSQL builds), and records what ran from the installed files outside a
checkout: sqlite and PostgreSQL operations, the missing-addon refusal, the
shipped typings and licence, the documented setup commands, and how
firecracker and ssh respond. Lists what did not run and the owner decisions
(PostgreSQL/TLS in published artifacts, glibc floor, publication, CI).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* docs(general): correct the Firecracker and SSH finding of the artifact report

The report said both platforms stayed selectable. That held for the tree the
artifacts were built from (d430474 plus four PRs) but not for the current
base, which contains the policy of layerfs-project#7 (b919f50, #577).
Replace the section with what a command built from the current base does
(not ready, Unsupported before any effect), drop the gap, and state in the
Source row that the artifacts predate that upstream change.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* docs(general): repeat the artifact qualification on the current base

The first run used artifacts built before #577 and later upstream changes.
Rebuild the default and PostgreSQL artifacts from the current base and record
the identity, hashes and results: Node 24 and 22, Python 3.10 to 3.14, the
command alone, the Firecracker/SSH policy on the installed command, and the
PostgreSQL and default builds against a port nothing listens on. The real
PostgreSQL server run could not be repeated because the Docker engine did
not answer; say so. The older sections stay as history.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

---------

Co-authored-by: root <root@wandanghe.localdomain>
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-authored-by: Mola-maker <noreply@example.invalid>
Mola-maker pushed a commit that referenced this pull request Nov 8, 2026
The report called them still selectable, quoting artifacts built before the
policy of layerfs-project#7 (b919f50, #577) landed. On a command built from
this base both are not ready and machine create / connect answer Unsupported
before any effect. Turn the row into a resolved fact and take it off the
open list.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Mola-maker added a commit that referenced this pull request Nov 8, 2026
…face report (#590)

* docs(versioned): add the 2.0.0 migration guide

Maps every old package, constructor, method and behaviour of 1.1.0 and the
unmerged PR 521 (packages and install, settings, methods, folder scope, bytes
and integers, errors, progress and exec output, doctor, the Workspace flow,
history features) to its 2.0 replacement or to why it is gone, with the file
or page that backs each row. Rows were re-checked against the current source
and docs, not copied; where the earlier investigation was out of date (workers
start on demand) the current text is used. The history features the owner
kept out of 2.0 are listed with the decision. Linked from the manual's
README.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* docs(versioned): add runnable Node, Python and shell examples

Four small files, one per front end (Node, Python sync, Python async,
the command), each doing the same mountless flow: store.create, project.init,
file write/read/list/edit, fork, diff, merge, commit.list and refusals
including two on a folder-scoped client. Each was run from an installed
artifact (npm pack + npm install, maturin build + pip install, the lone
binary) in a clean directory outside the checkout; the README quotes the real
output with ids and times trimmed, lists the artifact hashes, and writes the
Workspace route out marked NOT RUN with the refusal observed on this host.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* docs(general): add the 2.0.0 interface report

Pinned identity (base plus PRs 586, 588 and 589), capability matrix with
evidence links, compatibility table, known gaps each with its owning issue,
everything that was NOT RUN across the effort, and the checks run for the
report, including the base clippy failure (unused import ORDINAL_END in
layerfs-persistence), which was reproduced on the merge head.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* docs(general): list the failing tools test among the problems of the base

The fmt and guards job runs the unit tests of tools/, and
test_decode_observations fails on layerfs_v2_0_0 itself (58 != 55 for
section 13), on a tree whose tools/ is untouched. Name it next to the other
base failures so a reader does not take it for a result of this work.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* docs(general): firecracker and ssh are disabled by policy on this base

The report called them still selectable, quoting artifacts built before the
policy of layerfs-project#7 (b919f50, #577) landed. On a command built from
this base both are not ready and machine create / connect answer Unsupported
before any effect. Turn the row into a resolved fact and take it off the
open list.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Mola-maker <noreply@example.invalid>
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
@yifanxuaaa
yifanxuaaa deleted the fix/disable-firecracker-ssh branch November 18, 2026 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant