hermes-devcontainer-persistence

You preserve service state across dev container rebuilds by coordinating lifecycle hooks and automated backups, ensuring configuration and memories survive container restarts through external home volumes and workspace mounts.

Dev container lifecycle hooks manage auto-start by executing initializeCommand, onCreateCommand, postCreateCommand, and postStartCommand to orchestrate startup, trigger backups, and auto-restore state when the home volume is empty.

Yes, you can use external home volumes to back up agent configuration and memories by centralizing backups in a dedicated directory, integrated via post-start and cron scheduling for automated persistence.

The best way to restore agent services when the home volume is empty is to auto-restore from the centralized backup directory, with manual reconfiguration guidance provided if the backup is incomplete.

Dev container persistence includes disaster recovery guards for local development by validating backup integrity and automating restoration flows, ensuring configuration and state survive container restarts without manual intervention.

Agent configuration disappears after a dev container restart because state is not persisted to external volumes; implementing lifecycle hooks and automated backups ensures configuration and memories survive subsequent rebuilds.