langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #31899] fix(docker): persist IRIS data across container recreation using Durable %SYS #33461

New Issue
Closed
opened 2026-02-21 20:53:19 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:53:19 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/31899

State: closed
Merged: Yes

Important

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Fixes #31860

Fix IRIS Docker container losing all data when running docker compose down && up or upgrading the IRIS image version.

What Changed

  • Use ISC_DATA_DIRECTORY environment variable to enable IRIS Durable %SYS feature for proper data persistence
  • Change volume mount from ./volumes/iris:/opt/iris to ./volumes/iris:/durable
  • Remove flag file mechanism (.iris-configured) and make initialization script idempotent

Why It Matters

Previously, the IRIS container only persisted a flag file at /opt/iris, while the actual USER namespace data at /usr/irissys/mgr/user/ was lost on container recreation. This caused complete data loss for all IRIS users when upgrading Dify or recreating containers.

Technical Details

  • Durable %SYS: InterSystems IRIS's official mechanism for data persistence in containerized environments
  • ISC_DATA_DIRECTORY: Environment variable that tells IRIS where to store durable instance data
  • Idempotent initialization: The init script (password setup, etc.) can now run on every container start without side effects

Screenshots

N/A (Docker configuration change only)

Before After
... ...

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran make lint and make type-check (backend) and cd web && npx lint-staged (frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/31899 **State:** closed **Merged:** Yes --- > [!IMPORTANT] > > 1. Make sure you have read our [contribution guidelines](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) > 1. Ensure there is an associated issue and you have been assigned to it > 1. Use the correct syntax to link this PR: `Fixes #<issue number>`. ## Summary Fixes #31860 Fix IRIS Docker container losing all data when running `docker compose down && up` or upgrading the IRIS image version. ### What Changed - Use `ISC_DATA_DIRECTORY` environment variable to enable IRIS Durable %SYS feature for proper data persistence - Change volume mount from `./volumes/iris:/opt/iris` to `./volumes/iris:/durable` - Remove flag file mechanism (`.iris-configured`) and make initialization script idempotent ### Why It Matters Previously, the IRIS container only persisted a flag file at `/opt/iris`, while the actual USER namespace data at `/usr/irissys/mgr/user/` was lost on container recreation. This caused complete data loss for all IRIS users when upgrading Dify or recreating containers. ### Technical Details - **Durable %SYS**: InterSystems IRIS's official mechanism for data persistence in containerized environments - **ISC_DATA_DIRECTORY**: Environment variable that tells IRIS where to store durable instance data - **Idempotent initialization**: The init script (password setup, etc.) can now run on every container start without side effects ## Screenshots N/A (Docker configuration change only) | Before | After | |--------|-------| | ... | ... | ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `make lint` and `make type-check` (backend) and `cd web && npx lint-staged` (frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:53:19 -05:00
yindo closed this issue 2026-02-21 20:53:19 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#33461
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?