Skip to content

fix: preserve gVisor configuration across Lima restarts - #24

Merged
convee merged 2 commits into
mainfrom
fix/containerd-reboot-origin
Sep 6, 2026
Merged

convee merged 2 commits into
mainfrom
fix/containerd-reboot-origin

Conversation

@convee

@convee convee commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Preserve existing containerd runtime and registry settings during repeated Lima provisioning.
  • Add a stopped-VM-only migration for the exact legacy provision block, with saved-template readback.
  • Document recovery without rebuilding the cluster or lowering runtime isolation.

Validation

  • 51 focused tests: 50 passed, 1 Linux-only check skipped on macOS; all 8 new regression cases passed.
  • Real existing VM migration and restart: containerd configuration and cluster CA hashes unchanged.
  • Agent and Artifact Service pods can reach the independent Sandbox after restart.

No SDK revision or dependency pin changes. Existing operator changes are preserved; unknown provision blocks are rejected.

@convee
convee merged commit d056f7a into main Sep 6, 2026
12 checks passed
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