You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Track runtime ownership to prevent cross-runtime status corruption
When multiple runtimes coexist (e.g., podman and go-microvm), running
CLI commands with one runtime active permanently corrupts the status
files of workloads managed by the other runtime, marking them as
"unhealthy." This happens because the reconciliation logic assumes all
workloads belong to the single active runtime.
Add a RuntimeName field to RunConfig that records which runtime created
a workload, and a Name() method to the Runtime interface so the active
runtime can identify itself. During reconciliation, skip workloads whose
owning runtime differs from the active one. Legacy workloads without a
RuntimeName are conservatively treated as owned by the active runtime.
Fixes#4432
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
0 commit comments