I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
0.6.0
Ollama Version (if applicable)
No response
Operating System
Docker on Linux host
Browser (if applicable)
No response
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have listed steps to reproduce the bug in detail.
Expected Behavior
Expecting the main process to launch but it seems to crash without any obvious Debug log message to show why
Actual Behavior
The arm64 docker container for 0.6.0 keeps restarting, the log shows this repeating section
Loading WEBUI_SECRET_KEY from file, not provided as an environment variable.
Loading WEBUI_SECRET_KEY from .webui_secret_key
/app/backend/open_webui
/app/backend
/app
Steps to Reproduce
Launch 0.5.20 via Docker on an arm64 host
Upgrade to 0.6.0 via Docker and notice it crashes
Logs & Screenshots
See above for looping log section
Additional Information
No response
Originally created by @lowlyocean on GitHub (Apr 1, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12257
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
0.6.0
### Ollama Version (if applicable)
_No response_
### Operating System
Docker on Linux host
### Browser (if applicable)
_No response_
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have listed steps to reproduce the bug in detail.
### Expected Behavior
Expecting the main process to launch but it seems to crash without any obvious Debug log message to show why
### Actual Behavior
The arm64 docker container for 0.6.0 keeps restarting, the log shows this repeating section
```
Loading WEBUI_SECRET_KEY from file, not provided as an environment variable.
Loading WEBUI_SECRET_KEY from .webui_secret_key
/app/backend/open_webui
/app/backend
/app
```
### Steps to Reproduce
Launch 0.5.20 via Docker on an arm64 host
Upgrade to 0.6.0 via Docker and notice it crashes
### Logs & Screenshots
See above for looping log section
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-04-19 22:25:37 -05:00
Experenceied Same issue on arm64 platform on ghcr.io/open-webui/open-webui:main Imgage
<!-- gh-comment-id:2768058422 -->
@5418ly commented on GitHub (Apr 1, 2025):
Experenceied Same issue on arm64 platform on ghcr.io/open-webui/open-webui:main Imgage
I opened a shell in the container to run ulimit -c unlimited and then again to do apt update && apt install gdb && gdb -c core , which reports the following:
Core was generated by `/usr/local/bin/python /usr/local/bin/uvicorn open_webui.main:app --host 0.0.0.0'.
Program terminated with signal SIGILL, Illegal instruction.
For reference, the host is a Raspberry Pi 4
<!-- gh-comment-id:2768070871 -->
@lowlyocean commented on GitHub (Apr 1, 2025):
I opened a shell in the container to run `ulimit -c unlimited` and then again to do `apt update && apt install gdb && gdb -c core` , which reports the following:
```
Core was generated by `/usr/local/bin/python /usr/local/bin/uvicorn open_webui.main:app --host 0.0.0.0'.
Program terminated with signal SIGILL, Illegal instruction.
```
For reference, the host is a Raspberry Pi 4
After an apt install python3-dbg && gdb python 1, it shows the culprit as the "onnxruntime" python package. Can we pin this to the version that was used in 0.5.20 (which looks like onnxruntime==1.20.1) until the regression in 1.21.0 is fixed?
Thread 1 "uvicorn" received signal SIGILL, Illegal instruction.
0x0000007f57b428f4 in ?? () from /usr/local/lib/python3.11/site-packages/onnxruntime/capi/onnxruntime_pybind11_state.cpython-311-aarch64-linux-gnu.so
I can confirm that rolling back this package allows 0.6.0 to launch without SIGILL:
<!-- gh-comment-id:2768096512 -->
@lowlyocean commented on GitHub (Apr 1, 2025):
After an `apt install python3-dbg && gdb python 1`, it shows the culprit as the "onnxruntime" python package. Can we pin this to the version that was used in 0.5.20 (which looks like onnxruntime==1.20.1) until the regression in 1.21.0 is fixed?
```
Thread 1 "uvicorn" received signal SIGILL, Illegal instruction.
0x0000007f57b428f4 in ?? () from /usr/local/lib/python3.11/site-packages/onnxruntime/capi/onnxruntime_pybind11_state.cpython-311-aarch64-linux-gnu.so
```
I can confirm that rolling back this package allows 0.6.0 to launch without SIGILL:
```
docker exec open-webui pip install onnxruntime==1.20.1
```
I have a question how can I upgrade I'm using docker I have the 0.5.20 and I want to upgrade to the 0.6.0. any ideas?
<!-- gh-comment-id:2768318322 -->
@jfrisancho commented on GitHub (Apr 1, 2025):
I have a question how can I upgrade I'm using docker I have the 0.5.20 and I want to upgrade to the 0.6.0. any ideas?
<!-- gh-comment-id:2768394508 -->
@spydisec commented on GitHub (Apr 1, 2025):
> I have a question how can I upgrade I'm using docker I have the 0.5.20 and I want to upgrade to the 0.6.0. any ideas?
This will help you out:
https://docs.openwebui.com/getting-started/updating/
I tried a fresh installation with an empty volume for the Raspberry Pi 4 Docker, but I still have the same restarting error.
I tried an installation with my ARM-based MacBook Docker and that worked fine.
<!-- gh-comment-id:2769194120 -->
@DJMo13 commented on GitHub (Apr 1, 2025):
I tried a fresh installation with an empty volume for the Raspberry Pi 4 Docker, but I still have the same restarting error.
I tried an installation with my ARM-based MacBook Docker and that worked fine.
<!-- gh-comment-id:2769410665 -->
@lowlyocean commented on GitHub (Apr 1, 2025):
If you have a Raspberry Pi, try this (might need to try a few times in order for it to finish)
> I can confirm that rolling back this package allows 0.6.0 to launch without SIGILL:
>
> ```
> docker exec open-webui pip install onnxruntime==1.20.1
> ```
This is a somewhat similar issue as discussed in latest docker image does not work on rpi4. A workaround is to build a custom image as described here using the version of onnxruntime @lowlyocean mentions.
<!-- gh-comment-id:2770600997 -->
@adintegra commented on GitHub (Apr 1, 2025):
This is a somewhat similar issue as discussed in [latest docker image does not work on rpi4](https://github.com/open-webui/open-webui/discussions/4331). A workaround is to build a custom image as described [here](https://github.com/open-webui/open-webui/discussions/4331#discussioncomment-10401321) using the version of `onnxruntime` @lowlyocean mentions.
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 @lowlyocean on GitHub (Apr 1, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12257
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.0
Ollama Version (if applicable)
No response
Operating System
Docker on Linux host
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Expecting the main process to launch but it seems to crash without any obvious Debug log message to show why
Actual Behavior
The arm64 docker container for 0.6.0 keeps restarting, the log shows this repeating section
Steps to Reproduce
Launch 0.5.20 via Docker on an arm64 host
Upgrade to 0.6.0 via Docker and notice it crashes
Logs & Screenshots
See above for looping log section
Additional Information
No response
@5418ly commented on GitHub (Apr 1, 2025):
Experenceied Same issue on arm64 platform on ghcr.io/open-webui/open-webui:main Imgage
@misterwigglesworth commented on GitHub (Apr 1, 2025):
Same thing on my dietpi
@lowlyocean commented on GitHub (Apr 1, 2025):
I opened a shell in the container to run
ulimit -c unlimitedand then again to doapt update && apt install gdb && gdb -c core, which reports the following:For reference, the host is a Raspberry Pi 4
@lowlyocean commented on GitHub (Apr 1, 2025):
After an
apt install python3-dbg && gdb python 1, it shows the culprit as the "onnxruntime" python package. Can we pin this to the version that was used in 0.5.20 (which looks like onnxruntime==1.20.1) until the regression in 1.21.0 is fixed?I can confirm that rolling back this package allows 0.6.0 to launch without SIGILL:
@spydisec commented on GitHub (Apr 1, 2025):
Likewise not working in arm based, host is Raspberry Pi 4b.
@jfrisancho commented on GitHub (Apr 1, 2025):
I have a question how can I upgrade I'm using docker I have the 0.5.20 and I want to upgrade to the 0.6.0. any ideas?
@spydisec commented on GitHub (Apr 1, 2025):
This will help you out:
https://docs.openwebui.com/getting-started/updating/
@sinfallas commented on GitHub (Apr 1, 2025):
not working on Raspberry Pi 4b.
@DJMo13 commented on GitHub (Apr 1, 2025):
I tried a fresh installation with an empty volume for the Raspberry Pi 4 Docker, but I still have the same restarting error.
I tried an installation with my ARM-based MacBook Docker and that worked fine.
@lowlyocean commented on GitHub (Apr 1, 2025):
If you have a Raspberry Pi, try this (might need to try a few times in order for it to finish)
@adintegra commented on GitHub (Apr 1, 2025):
This is a somewhat similar issue as discussed in latest docker image does not work on rpi4. A workaround is to build a custom image as described here using the version of
onnxruntime@lowlyocean mentions.