Docker container crash and restart all time

[MitsuhaKitsune]

Bug Report

When I try to start the docker container following the readme and guide, the container start to restart in loop constantly.

Description

Bug Summary:
Docker container crash and restart on startup

Steps to Reproduce:
Just run this command:

docker run -d --network=host -v open-webui:/app/backend/data -e OLLAMA_API_BASE_URL=http://192.168.1.10:11434/api --name open-webui --restart always ghcr.io/open-webui/open-webui:main

Expected Behavior:
Docker container start successfull and let me open the web UI

Actual Behavior:
Docker container crash and restart on startup

Environment

• Operating System: Debian 12
• Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0]

Reproduction Details

Confirmation:

• I have read and followed all the instructions provided in the README.md.
• I have reviewed the troubleshooting.md document.
• I have included the browser console logs.
• I have included the Docker container logs.

Logs and Screenshots

Browser Console Logs:
[Include relevant browser console logs, if applicable]

Docker Container Logs:

 No WEBUI_SECRET_KEY provided
 

 Generating WEBUI_SECRET_KEY
 

 Loading WEBUI_SECRET_KEY from .webui_secret_key
 

 /usr/local/lib/python3.11/site-packages/pydantic/_internal/_fields.py:151: UserWarning: Field "model_max_budget" has conflict with protected namespace "model_".
 

 
 

 You may be able to resolve this warning by setting `model_config['protected_namespaces'] = ()`.
 

   warnings.warn(
 

 No WEBUI_SECRET_KEY provided
 

 Generating WEBUI_SECRET_KEY
 

 Loading WEBUI_SECRET_KEY from .webui_secret_key
 

 /usr/local/lib/python3.11/site-packages/pydantic/_internal/_fields.py:151: UserWarning: Field "model_max_budget" has conflict with protected namespace "model_".
 

 
 

 You may be able to resolve this warning by setting `model_config['protected_namespaces'] = ()`.
 

   warnings.warn(
 

 No WEBUI_SECRET_KEY provided
 

 Loading WEBUI_SECRET_KEY from .webui_secret_key
 

 /usr/local/lib/python3.11/site-packages/pydantic/_internal/_fields.py:151: UserWarning: Field "model_max_budget" has conflict with protected namespace "model_".
 

 
 

 You may be able to resolve this warning by setting `model_config['protected_namespaces'] = ()`.
 

   warnings.warn(

Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]

Installation Method

Docker

Additional Information

Logs don't provide any aditional info

Note

If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

[MitsuhaKitsune]

I try to run the webui from source code, and I can see "Illegal instruction" that crash the program.

Uncompatible hardware maybe? I explain better my enviroment:

I just trying to run the webui on one of my servers of my LAN (HP ProLiant MicroServer G7 HSTNS 5151 N54L), but didn't have a recent CPU or GPU to run AI, just want the UI, the ollama server are on other hardware of my LAN.

[tjbck]

Hmm, unable to reproduce the issue at all. Might have something to do with your hardware configuration, moving to discussion.

[MitsuhaKitsune]

Illegal Instruction are produced when a processor didn't support the instruction set of software, the CPU of this server its a AMD Turion II Neo N54L.

As I know, llama as like the most AI projects need atleast AVX2 CPU's or cuda GPU, but I only running this project on the server (the ollama server are in another PC).

I try to connect from this server to the ollama in a simple vue webpage through the API and connection works, so I discard any connection problem.

As I understand, this project don't have any AI process, its just a web interface to connect to ollama API, so seems strange that throw this error, but some dependency can produce incompatibilities with this CPU if need more recent instruction sets.

Unafortunally I try to do a fast research but can't found what produce this.

[tjbck]

Try installing without docker: https://docs.openwebui.com/getting-started/#how-to-install-without-docker

[MitsuhaKitsune]

I tried it, but unafortunally crash on startup too, the unic difference between docker and source code, it's that on source code I can read "Illegal Instruction" before crash,

[amartinAIDIMME]

I have a similar problem in windows:
#942

[bladethirst]

I hava a similar problem in centos 7.9. I run it with docker.

[bladethirst]

I found the problem related to docker version. with parameter "--security-opt seccomp:unconfined" or "–privileged=true" when running container can fix the problem.

[elabz]

@bladethirst , could you please specify what exactly you did to fix the problem? My attempts to run with --security-opt seccomp:unconfined did not change anything at all - container keeps restarting.

docker run -d --network=host -v open-webui:/app/backend/data -e OLLAMA_API_BASE_URL=http://192.168.0.151:11434/api --name open-webui-1 --restart always --security-opt seccomp:unconfined ghcr.io/open-webui/open-webui:main

adding privileged: true to docker-compose.yaml also yielded no results

Would appreciate your input on this. Thanks!

[justinh-rahb]

Considering @bladethirst is using CentOS, it's likely his problem was caused by AppArmor preventing an unprivileged container from accessing the host network. Are you also using CentOS or another distro with AppArmor enabled?

I think both of you would be better off to investigate why the normal overlay network and published port method isn't working, as setting --network=host is often a band-aid fix for something else.

[elabz]

@justinh-rahb - I am not sure network is the problem as the docker-compose.yaml it starts off of (if not using the command above) has

    extra_hosts:
      - host.docker.internal:host-gateway

And leads to the same constant restarting

[elabz]

Oh, and yes, I am on Ubuntu 22.04 server
Linux ash 5.15.0-97-generic #107-Ubuntu SMP Wed Feb 7 13:26:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

[fevolq]

我也遇到了这个问题，在基于wsl的ubuntu机器上，通过docker启动的，网页无法访问

[elabz]

@tjbck , could we move this back to issues please? It's still happening on the latest update, with or without GPU. All the latest CUDA and NVIDIA drivers (although this should not be affecting anything on open-webui container?

Can someone suggest a way to enable more descriptive error log? The docker logs open-webui only contains warnings, not errors (mentioned above in this thread)

[elabz]

There is an error on dmesg that may correlate to this - uvicorn breaks on something:

traps: uvicorn[20563] trap invalid opcode ip:7f07bf3597cc sp:7ffcf5a50f88 error:0 in libctranslate2-de03ae65.so.4.0.0[7f07bf206000+2d7e000]

Could this be relevant?

[elabz]

🤔 I turned out to be 6GB, not even 8GB. However, shutting down ollama and only starting open-webui does not fix anything. I ran it with top running and the memory usage never goes above 1GB

[elabz]

... and another similar question: can it run on CPU with 4 cores?

$ lshw -c cpu
WARNING: you should run this program as super-user.
  *-cpu
       product: AMD Phenom(tm) 9550 Quad-Core Processor
       vendor: Advanced Micro Devices [AMD]
       physical id: 1
       bus info: cpu@0
       version: 16.2.3
       width: 64 bits
       capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs hw_pstate vmmcall npt lbrv svm_lock
       configuration: microcode=16777357
WARNING: output may be incomplete or inaccurate, you should run this program as super-user.

[justinh-rahb]

That CPU is old enough to get a driver's license! 👀 Sorry but time to upgrade, your CPU doesn't even support AVX1, let alone AVX2.

[elabz]

Thank you for checking, @justinh-rahb , I am still very curious about running ollama on it, perhaps serving open-webui from a different machine

[justinh-rahb]

Welcome to give that a go, but I don't see it going much better. Without at least some acceleration like AVX, llama.cpp is dog slow.

[kelley01]

I am having the same issue. I had WebUI working, then I changed my Docker root directory from /var/lib/docker to a secondary hard drive. Now open-webui will not stay up. It keeps stopping and restarting. Other Docker containers are working just fine.

[viba1]

Same problem here from a fresh docker installation. I noticed that the problem systematically occurs when I download files.