mirror of
https://github.com/open-webui/open-webui.git
synced 2026-11-17 03:03:27 -06:00
[GH-ISSUE #23449] issue: SOS - I'm completely stuck and desperately need help! I've been trying to fix this for hours with no success. Please help me! #123298
Reference in New Issue
Block a user
Originally created by @teddy911405 on GitHub (Apr 6, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23449
https://ibb.co/0VBc2hrz
https://ibb.co/dsHL6dcH
Check Existing
Installation Method
Docker
Open WebUI Version
v0.6.16
Ollama Version (if applicable)
No response
Operating System
Ubuntu 22.04.5 LTS
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Running
docker stop open-webui && docker rm open-webuishould completely stop and remove the Open WebUI container, freeing port 8080.Actual Behavior
After
docker rm, the container disappears fromdocker ps -a, but port 8080 remains occupied by a Python/uvicorn process. The process is a ghost container running at the containerd level (containerd-shim-runc-v2) that auto-restarts every time it is killed.Steps to Reproduce
Logs & Screenshots
$ sudo ss -tlnp | grep 8080
LISTEN 0 2048 0.0.0.0:8080 0.0.0.0:* users=(("python3",pid=5404,fd=20))
$ ps -ef | grep containerd-shim
root 5382 1 0 17:27 ? /usr/bin/containerd-shim-runc-v2 -namespace moby -id 60c5708762c65d740ca25e5a5339398aca9617c5180f0808d1f1c0ce2f872682 -address /run/containerd/containerd.sock
$ sudo ctr -n moby containers rm 60c5708762c6...
Error: cannot delete a non stopped container
Additional Information
🆘 SOS - I'm completely stuck and desperately need help! I've been trying to fix this for hours with no success. Please help me!
[HELP] Open WebUI ghost container stuck in containerd - docker ps -a shows nothing but service still running
Environment
Problem Description
I originally installed Open WebUI using Docker with the following command:
I later tried to update by running
docker stop open-webui && docker rm open-webui. After that,docker ps -ashows no open-webui container, but http://127.0.0.1:8080 is still accessible and working!Investigation
Checking port 8080:
Tracing the parent process:
I found a ghost container at the containerd level (container ID:
60c5708762c6). Docker no longer recognizes it, but containerd keeps it running and auto-restarts it every time I kill the process.What I've Already Tried (All Failed)
sudo kill -9 <pid>→ process auto-restarts immediatelysudo systemctl restart docker→ process reappears after restartsudo ctr -n moby tasks kill <id>→ process still revivessudo ctr -n moby containers rm <id>→ Error: cannot delete a non stopped containersudo ctr -n moby tasks delete --force <id>→ Error: cannot delete a deleted process: not foundsudo pkill -9 -f open_webui→ process auto-restartswsl --shutdownthen reopen WSL → process still appearssudo pip3 uninstall open-webui→ WARNING: open-webui is not installedsudo pip3 show open-webui→ Package not found (but process is clearly still running as root via uvicorn!)Questions
docker rm?pip3 showsays not installed but the process is clearly running as root via uvicorn)Any help is appreciated. Thank you so much! 🙏
@dlingerfelt22 commented on GitHub (Apr 6, 2026):
This looks like a Docker/containerd desynchronization issue rather than a bug with Open WebUI. WSL isn't the best at keeping daemons synchronized. Because you started the docker image with the
--restart alwaysflag, thecontainerddaemon only knows that state and will attempt to restart the process any time the container goes down, even thoughdockerdhas lost track of it.I would kill the container daemon and docker first:
sudo systemctl stop dockersudo systemctl stop containerdThen kill the shim and the uvicorn processes so they don't auto-restart:
sudo pkill -9 -f containerd-shimsudo pkill -9 -f uvicornThen remove the specific container state you showed in your log:
sudo rm -rf /run/containerd/io.containerd.runtime.v2.task/moby/60c5708762c65d740ca25e5a5339398aca9617c5180f0808d1f1c0ce2f872682Finally, restart the daemons:
sudo systemctl start containerdsudo systemctl start docker@teddy911405 commented on GitHub (Apr 7, 2026):
The ghost container is gone from
docker ps -a, and I was able to launch a new Open WebUI container on port 3000.However, http://127.0.0.1:8080/ is still accessible and running!
Checking the process:
Something is still serving Open WebUI on port 8080, but I cannot find where it is installed.
@teddy911405 commented on GitHub (Apr 7, 2026):
Thank you for the suggestion!
I actually have screenshot records confirming that Open WebUI was
originally installed via Docker.
I also already checked with pip and it returns not found:
@dylanmorris1231ho-spec commented on GitHub (Apr 7, 2026):
Thanks for providing the additional details and command outputs.
On Tue, Apr 7, 2026, 7:21 AM teddy911405 @.***> wrote: