Description
Container state is not persisted across shutdowns. Container data, environment variables, and configuration are lost on restart. Users cannot resume or checkpoint running containers.
Steps to Reproduce
- Start container with custom configuration and data
- Container running and processing requests
- System restarts or container stopped
- Restart container
- No state or configuration from previous run
- Data lost
Environment Information
- Persistence: Not implemented
- Storage: No checkpoint/snapshot
- State management: In-memory only
- Restart: Fresh container
Expected Behavior
- Container state saved on shutdown
- State restored on restart
- Checkpoint/snapshot capability
- Data persistence across restarts
Actual Behavior
- No state persistence
- Data lost on shutdown
- Fresh container on restart
- No recovery option
Code Reference
- File:
daemon/container.rs
- Missing: State persistence logic
- Missing: Checkpoint mechanism
- Missing: Snapshot storage
Additional Context
Level 2 feature gap. Fix requires:
- Implementing container state persistence
- Checkpoint/snapshot mechanism
- State recovery on restart
- Testing state persistence
Suggested Labels
feature-request, persistence, state-management, reliability, checkpointing
Description
Container state is not persisted across shutdowns. Container data, environment variables, and configuration are lost on restart. Users cannot resume or checkpoint running containers.
Steps to Reproduce
Environment Information
Expected Behavior
Actual Behavior
Code Reference
daemon/container.rsAdditional Context
Level 2 feature gap. Fix requires:
Suggested Labels
feature-request,persistence,state-management,reliability,checkpointing