github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-06-07 17:28:41 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

Older image when download. #2780

New Issue
Closed
opened 2025-11-11 15:14:15 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 15:14:15 -06:00
Owner
Copy Link

Originally created by @ns-bcr on GitHub (Nov 22, 2024).

Bug Report

Installation Method

I installed Open WebUI using Docker with the following command:

docker run -d -p 3000:8080 --gpus all -v open-webui:/app/backend/data --name open-webui ghcr.io/open-webui/open-webui:cuda

Environment

  • Open WebUI Version: v0.3.32
  • Operating System: Ubuntu 24.4.0
  • Browser (if applicable): Opera GX

Confirmation

  • I have read and followed all the instructions provided in README.md.
  • I am using the latest versions of both Open WebUI and Ollama.
  • I have attached browser console logs.
  • I have attached the Docker container logs.
  • I have included detailed reproduction steps in the "Reproduction Details" section.

Expected Behavior

I noticed a new version (v0.4.3) was available. Initially, I couldn’t find the update page. To resolve this, I removed my existing Docker instance and reinstalled the Docker image.

Actual Behavior

Instead of getting the latest version (v0.4.3), I ended up with an older version than what I had previously installed (v0.3.32).

Additionally:

  • I lost all my data. Thankfully, I had backed up most of it.
  • However, I am unable to download the config.yaml file.

Bug Summary

This issue might be related to a missing migration step. I saw a reference to migrations in the documentation, but since I can’t access the config.yaml, I couldn’t proceed.

Reproduction Details

Steps to Reproduce:

  1. Pull the latest Docker image: 
    docker pull ghcr.io/open-webui/open-webui:main
  2. Run the container: 
    docker run -d -p 3000:8080 --gpus all -v open-webui:/app/backend/data --name open-webui ghcr.io/open-webui/open-webui:cuda

Logs and Screenshots

Browser Console Logs:
Browser Console Logs Screenshot

Additional Note

It seems the issue might be resolved through a migration step, but without access to the config.yaml file, I am unable to confirm this.

Originally created by @ns-bcr on GitHub (Nov 22, 2024). # Bug Report --- ## Installation Method I installed Open WebUI using Docker with the following command: ```bash docker run -d -p 3000:8080 --gpus all -v open-webui:/app/backend/data --name open-webui ghcr.io/open-webui/open-webui:cuda ``` --- ## Environment - **Open WebUI Version:** v0.3.32 - **Operating System:** Ubuntu 24.4.0 - **Browser (if applicable):** Opera GX --- ## Confirmation - [x] I have read and followed all the instructions provided in `README.md`. - [ ] I am using the latest versions of both Open WebUI and Ollama. - [x] I have attached browser console logs. - [ ] I have attached the Docker container logs. - [x] I have included detailed reproduction steps in the "Reproduction Details" section. --- ## Expected Behavior I noticed a new version (v0.4.3) was available. Initially, I couldn’t find the update page. To resolve this, I removed my existing Docker instance and reinstalled the Docker image. --- ## Actual Behavior Instead of getting the latest version (v0.4.3), I ended up with an older version than what I had previously installed (v0.3.32). Additionally: - I lost all my data. Thankfully, I had backed up most of it. - However, I am unable to download the `config.yaml` file. --- ## Bug Summary This issue might be related to a missing migration step. I saw a reference to migrations in the documentation, but since I can’t access the `config.yaml`, I couldn’t proceed. --- ## Reproduction Details ### Steps to Reproduce: 1. Pull the latest Docker image: ```bash docker pull ghcr.io/open-webui/open-webui:main ``` 2. Run the container: ```bash docker run -d -p 3000:8080 --gpus all -v open-webui:/app/backend/data --name open-webui ghcr.io/open-webui/open-webui:cuda ``` --- ## Logs and Screenshots **Browser Console Logs:** ![Browser Console Logs Screenshot](https://github.com/user-attachments/assets/98303975-6a7a-4294-a541-8d114e126989) --- ## Additional Note It seems the issue might be resolved through a migration step, but without access to the `config.yaml` file, I am unable to confirm this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#2780
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?