Skip to content

fix: persist Docker runtime data safely - #46

Merged
EvanProgramming merged 1 commit into
mainfrom
codex/issue-22-docker-persistence
Sep 3, 2026
Merged

EvanProgramming merged 1 commit into
mainfrom
codex/issue-22-docker-persistence

Conversation

@EvanProgramming

Copy link
Copy Markdown
Owner

Summary

  • configure the non-root image to store SQLite and derived indexes under /data
  • exclude local runtime data, caches, credentials, and build output from Docker context
  • add a real replace-container persistence smoke test and document the durable volume path in all READMEs

Validation

  • make check
  • make lint
  • make test (119 tests)
  • git diff --check
  • real two-process SQLite write/restart/API recovery smoke passed
  • Docker smoke is configured as the GitHub Actions docker-persistence job; Docker is unavailable on the local machine

Fixes #22

@EvanProgramming
EvanProgramming merged commit 7110139 into main Sep 3, 2026
3 checks passed
@EvanProgramming
EvanProgramming deleted the codex/issue-22-docker-persistence branch September 3, 2026 14:23
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.

fix: correct Docker data persistence and exclude local runtime data from image context

1 participant