docker compose up
[+] Running 2/2
✔ Volume "open-webui_open-webui" Created 0.0s
✔ Container open-webui Created 0.2s
Attaching to open-webui
open-webui | Loading WEBUI_SECRET_KEY from file, not provided as an environment variable.
open-webui | Generating WEBUI_SECRET_KEY
open-webui | Loading WEBUI_SECRET_KEY from .webui_secret_key
open-webui exited with code 135
open-webui exited with code 135
Is there a way to recover without a full reset ?
Originally created by @papiche on GitHub (Nov 13, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/6905
# Update fails
After an upgrade ...
```
docker pull ghcr.io/open-webui/open-webui:main
docker stop open-webui
docker rm open-webui
docker run -d --network=host -v open-webui:/app/backend/data -e OLLAMA_BASE_URL=http://127.0.0.1:11434 -e PORT=11642 --name open-webui --restart always ghcr.io/open-webui/open-webui:main
```
docker service is failing
```
docker compose up
[+] Running 2/2
✔ Volume "open-webui_open-webui" Created 0.0s
✔ Container open-webui Created 0.2s
Attaching to open-webui
open-webui | Loading WEBUI_SECRET_KEY from file, not provided as an environment variable.
open-webui | Generating WEBUI_SECRET_KEY
open-webui | Loading WEBUI_SECRET_KEY from .webui_secret_key
open-webui exited with code 135
open-webui exited with code 135
```
Is there a way to recover without a full reset ?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @papiche on GitHub (Nov 13, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/6905
Update fails
After an upgrade ...
docker service is failing
Is there a way to recover without a full reset ?