Pipelines persistency #84

New Issue

2026-02-15T19:16:06-05:00

yindo commented

2026-02-15 19:16:06 -05:00

Originally created by @jkleinkauff on GitHub (May 9, 2025).

Hey friends!
This is not a bug I think.

I've deployed OWUI and the pipelines module using this helm chart. To upload new pipelines to the platform, I have an initContainer in pipelines.extraInitContainer. The yaml also has the volume configuration to mount it to the pipelines folder properly.

  extraInitContainers:
    - name: fetch-github-folder
      image: appropriate/curl
      command:
        - sh
        - -c
        - |
          set -e
          echo "Fetching files from GitHub branch..."
          we clone the gh dir here.

This setup works ok. The problem is that whenever the pipeline pod is rebooted, any changes we've made to the Pipeline Valves are being overwritten by the default values configured in the pipe script. I understand why this is happening, since every time the pod boots it will clone the repo again. My question is if there is a better way of cloning the github repo or perhaps something to persist the pipeline changes?

Chart version: 6.0.0

Thank you!.

Originally created by @jkleinkauff on GitHub (May 9, 2025). Hey friends! This is not a bug I think. I've deployed OWUI and the pipelines module using this helm chart. To upload new pipelines to the platform, I have an initContainer in pipelines.extraInitContainer. The yaml also has the volume configuration to mount it to the pipelines folder properly. ``` extraInitContainers: - name: fetch-github-folder image: appropriate/curl command: - sh - -c - | set -e echo "Fetching files from GitHub branch..." we clone the gh dir here. ``` This setup works ok. The problem is that whenever the pipeline pod is rebooted, any changes we've made to the Pipeline Valves are being overwritten by the default values configured in the pipe script. I understand why this is happening, since every time the pod boots it will clone the repo again. My question is if there is a better way of cloning the github repo or perhaps something to persist the pipeline changes? Chart version: 6.0.0 Thank you!.

yindo added the bug label 2026-02-15 19:16:06 -05:00

yindo referenced this issue

2026-02-15 19:16:41 -05:00

[PR #84] [MERGED] FIX: ollama url and env vars when ollama.enabled=False #168

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: open-webui/helm-charts#84