Skip to content

Prevent recording/data loss on Docker container recreation by declaring persistent /nvr volume#3

Draft
Copilot wants to merge 3 commits into
mainfrom
copilot/check-docker-container-recordings
Draft

Prevent recording/data loss on Docker container recreation by declaring persistent /nvr volume#3
Copilot wants to merge 3 commits into
mainfrom
copilot/check-docker-container-recordings

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 30, 2026

Containerized deployments could lose recordings and metadata if data paths were not persisted outside the container filesystem. This update makes persistence requirements explicit in both image definition and operator docs.

  • Docker image persistence contract

    • Added an explicit Docker volume declaration for runtime state:
      RUN mkdir -p /nvr
      VOLUME ["/nvr"]
  • Persistence guidance in docs

    • Updated recording.storage_path guidance to clarify that Docker deployments must mount persistent storage for the configured recording path (default under /nvr).
    • Strengthened Docker run section language to state that recordings + SQLite DB are lost when persistent mounts are omitted, and clarified behavior for custom storage paths outside /nvr.

Copilot AI and others added 2 commits March 30, 2026 13:14
Copilot AI changed the title [WIP] Investigate docker container restart behavior for recordings Prevent recording/data loss on Docker container recreation by declaring persistent /nvr volume Mar 30, 2026
Copilot AI requested a review from atmelmicro March 30, 2026 13:19
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.

2 participants