I need an authoritative way to establish what OrbStack will resume or initialize before starting an existing engine, while preserving retained workloads and volumes.
Installed application: OrbStack 2.2.3, build 20963, arm64. The installed CLI contains VCS revision c83556b0ef8f1ba9a33abbb194622b6b7a1c0307.
The engine is stopped. A bounded offline inspection, without mounting or booting the data image, observed:
- One manager
ContainerRecord in the containers bucket of /data/scon/store.db: the built-in Docker machine, with persisted State = running.
- No user-container records in the inspected Docker/containerd stores or active task directories.
- Nine retained anonymous Docker volumes, with driver
local and null options.
- A retained Kubernetes CoreDNS manifest, but no observed K3s server database.
These are observations from task-authored parsers, not a claim that this census is complete or sufficient for safe startup. I have not started the engine to test them.
Could you provide documentation or a procedure applicable to this build that answers:
- How does the startup manager interpret the persisted built-in Docker
State = running record? What other records or host settings control restoration and automatic initialization?
- What is the complete offline census for Linux machines, Docker containers/plugins/Swarm and Kubernetes? Can residual Kubernetes files cause initialization without a manager container record?
- What changes can startup make to retained Docker volume contents or their metadata when no user containers exist? How can preservation be established before startup?
- Is there a supported read-only offline inspection/export or startup mode that provides this proof without changing shared settings or retained state?
A statement that normal startup is generally safe would not resolve these specific preservation requirements. Version applicability and explicit limits would help. No diagnostic archive, private volume contents, credentials or source repository material is attached.
I need an authoritative way to establish what OrbStack will resume or initialize before starting an existing engine, while preserving retained workloads and volumes.
Installed application: OrbStack 2.2.3, build 20963, arm64. The installed CLI contains VCS revision
c83556b0ef8f1ba9a33abbb194622b6b7a1c0307.The engine is stopped. A bounded offline inspection, without mounting or booting the data image, observed:
ContainerRecordin thecontainersbucket of/data/scon/store.db: the built-in Docker machine, with persistedState = running.localand null options.These are observations from task-authored parsers, not a claim that this census is complete or sufficient for safe startup. I have not started the engine to test them.
Could you provide documentation or a procedure applicable to this build that answers:
State = runningrecord? What other records or host settings control restoration and automatic initialization?A statement that normal startup is generally safe would not resolve these specific preservation requirements. Version applicability and explicit limits would help. No diagnostic archive, private volume contents, credentials or source repository material is attached.