Running private LLMs on a P51 Thinkpad using Windows WSL.
TL:DR: Install Open WebUI on Docker running on Ubuntu installed in WSL on Windows 10. Pull llama3.1, gemma2 and other LLM manifests and personalize with your data. Forward port 3000 to the WSL IP address and access any LLM model from your private LAN on any web browser. QED.
MDS specializes in deploying offline LLMs into private servers in private Data Centers to access local secure data as an additional source of data for the LLM of choice, whether that is LLama, Gemma, Mistral and others. The ready models can be run on any hardware, within reason, albeit a bit slow at times. Speed costs and sometimes you just need to Sunday cruise.
This demo install is on a clean installation of Windows 10 on a Lenovo P51 laptop. It is not powerful at all but sufficient as a demonstration. LLMs usually run on powerful Linux Servers but this laptop runs best as Windows 10 machine built as a recovery workstation using the official Lenovo image creatin process. Therefore we will use Windows Subsystem for Linux (WSL). Good enough.
Windows must be above version 1902 to be able to run WSL 2.
To check run winver from the run command in Windows.
The next step is to install WSL.
Go to Windows Features and add the Virtual Machine Platform and Windows Subsystem for Linux
Install and restart.
You can also install the components via an Admin Powershell.
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
PS C:\WINDOWS\system32>
>> dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
>>
Deployment Image Servicing and Management tool
Version: 10.0.19041.3636
Image Version: 10.0.19045.4894
Enabling feature(s)
[==========================100.0%==========================]
The operation completed successfully.
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
PS C:\WINDOWS\system32> dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
Deployment Image Servicing and Management tool
Version: 10.0.19041.3636
Image Version: 10.0.19045.4894
Enabling feature(s)
[==========================100.0%==========================]
The operation completed successfully.
Now run the update
wsl --update
Upgrade to WSL 2.
Search for WSL2 Linux kernel update package for x64 machines.
Now install the update
Set WSL 2 as the default.
In powershell issue this command: wsl –set-default-version 2
PS C:\WINDOWS\system32> wsl --set-default-version 2
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
The operation completed successfully.
PS C:\WINDOWS\system32>
Install Ubuntu
You can install a specific version or the current LTS version Ubuntu 22.04.3 LTS (jammy). Simply use this command:
wsl –install -d Ubuntu
PS C:\WINDOWS\system32> wsl --install -d Ubuntu
Installing: Ubuntu
Ubuntu has been installed.
Launching Ubuntu...
Installing, this may take a few minutes...
Please create a default UNIX user account. The username does not need to match your Windows username.
For more information visit: https://aka.ms/wslusers
Enter new UNIX username: mds
New password:
Retype new password:
passwd: password updated successfully
The operation completed successfully.
Installation successful!
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
Welcome to Ubuntu 22.04.3 LTS (GNU/Linux 5.15.153.1-microsoft-standard-WSL2 x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
This message is shown once a day. To disable it please create the
/home/mds/.hushlogin file.
mds@Rayd-P51:~$
Launch an Ubuntu Console.
Now install ollama.
Use the following command:
curl -fsSL https://ollama.com/install.sh | sh
mds@Rayd-P51:~$ ollama
>>> Installing ollama to /usr/local
[sudo] password for mds:
>>> Downloading Linux amd64 bundle
######################################################################## 100.0%##O#-# ######################################################################## 100.0%
>>> Creating ollama user...
>>> Adding ollama user to render group...
>>> Adding ollama user to video group...
>>> Adding current user to ollama group...
>>> Creating ollama systemd service...
>>> Enabling and starting ollama service...
Created symlink /etc/systemd/system/default.target.wants/ollama.service → /etc/systemd/system/ollama.service.
>>> Nvidia GPU detected.
>>> The Ollama API is now available at 127.0.0.1:11434.
>>> Install complete. Run "ollama" from the command line.
mds@Rayd-P51:~$
Next run the ollama serve command
ollama serve
Error: listen tcp 127.0.0.1:11434: bind: address already in use
With later versions of Ubuntu ollama will start automatically and the ollama serve command is not required. To dig a bit deeper you can follow these commands but it is optional!
mds@Rayd-P51:~$ systemctl status ollama
mds@Rayd-P51:~$ systemctl stop ollama
mds@Rayd-P51:~$ systemctl start ollama
mds@Rayd-P51:~$ systemctl status ollama
● ollama.service - Ollama Service
Loaded: loaded (/etc/systemd/system/ollama.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2024-09-25 17:20:53 +08; 5min ago
Main PID: 663 (ollama)
Tasks: 15 (limit: 38404)
Memory: 2.6G
CGroup: /system.slice/ollama.service
└─663 /usr/local/bin/ollama serve
Sep 25 17:20:53 Rayd-P51 ollama[663]: Your new public key is:
Sep 25 17:20:53 Rayd-P51 ollama[663]: ssh-ed25519 AAAAC3N......
Sep 25 17:20:53 Rayd-P51 ollama[663]: 2024/09/25 17:20:53 routes.go:1153: INFO server config env="map[CUDA_VISIBLE_DEVI>
Sep 25 17:20:53 Rayd-P51 ollama[663]: time=2024-09-25T17:20:53.881+08:00 level=INFO source=images.go:753 msg="total blo>
Sep 25 17:20:53 Rayd-P51 ollama[663]: time=2024-09-25T17:20:53.881+08:00 level=INFO source=images.go:760 msg="total unu>
Sep 25 17:20:53 Rayd-P51 ollama[663]: time=2024-09-25T17:20:53.882+08:00 level=INFO source=routes.go:1200 msg="Listenin>
Sep 25 17:20:53 Rayd-P51 ollama[663]: time=2024-09-25T17:20:53.882+08:00 level=INFO source=common.go:135 msg="extractin>
Sep 25 17:21:04 Rayd-P51 ollama[663]: time=2024-09-25T17:21:04.764+08:00 level=INFO source=common.go:49 msg="Dynamic LL>
Sep 25 17:21:04 Rayd-P51 ollama[663]: time=2024-09-25T17:21:04.764+08:00 level=INFO source=gpu.go:199 msg="looking for >
Sep 25 17:21:07 Rayd-P51 ollama[663]: time=2024-09-25T17:21:07.216+08:00 level=INFO source=types.go:107 msg="inference >
lines 1-19/19 (END)
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAA....
netstat -aon | findstr :11434
Microsoft Windows
[Version 10.0.19045.4894]
(c) Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>netstat -aon | findstr :11434
TCP
127.0.0.1:11434 0.0.0.0:0 LISTENING 2680
C:\WINDOWS\system32>taskkill /F /PID 2680
SUCCESS: The process
with PID 2680 has been terminated.
Pull llama3.1
mds@Rayd-P51:~$ ollama pull llama3.1:latest
pulling manifest
pulling 8eeb52dfb3bb... 100% ▕████████████████████████████████████████████████████████▏ 4.7 GB
pulling 948af2743fc7... 100% ▕████████████████████████████████████████████████████████▏ 1.5 KB
pulling 0ba8f0e314b4... 100% ▕████████████████████████████████████████████████████████▏ 12 KB
pulling 56bb8bd477a5... 100% ▕████████████████████████████████████████████████████████▏ 96 B
pulling 1a4c3c319823... 100% ▕████████████████████████████████████████████████████████▏ 485 B
verifying sha256 digest
writing manifest
success
mds@Rayd-P51:~$ ollama list
NAME ID SIZE MODIFIED
llama3.1:latest 42182419e950 4.7 GB 35 seconds ago
Ready to run your first Local AI LLM?
ollama run llama3.1:latest
Testing llama 3.
>>> how long would it take to walk from cairo to jarusalem
Let's calculate the approximate time it would take to walk from Cairo, Egypt to Jerusalem, Israel.
Assuming a steady pace of about 5 kilometers per hour (3.1 miles per hour), which is a reasonable walking speed
for an adult with moderate fitness level.
**Distance:**
The distance between Cairo and Jerusalem is approximately:
* By road: around 340 km (211 miles)
* Overland, using existing trails or roads: around 350-400 km (217-249 miles)
For simplicity, let's use the shorter distance of 340 km.
**Walking hours per day:**
Let's assume you'll walk for about 8 hours a day, with some rest and sightseeing breaks in between. This is a
reasonable estimate, considering you'd want to get enough sleep, eat well, and enjoy the scenic views along the
way!
**Total walking days:**
To calculate the total number of walking days, let's divide the distance by your daily walking hours:
340 km ÷ 5 km/h = 68 hours
68 hours ÷ 8 hours/day = approximately 9-10 days
So, assuming you'll walk for about 8 hours a day and taking into account some rest days, it would take around
**9-10 days** to cover the distance from Cairo to Jerusalem on foot.
Please note that this is just an estimate, and actual walking times may vary depending on several factors, such
as:
* Terrain difficulty (e.g., desert, hills, urban areas)
* Weather conditions
* Your physical fitness level and endurance
* Rest and sightseeing breaks
Keep in mind that this is a rough estimate, and you should always prioritize your safety and well-being when
embarking on long-distance walking adventures!
This took about two minutes to display
>>> /bye
It was nice chatting with you about Olly-Ollama (just kidding, I had no idea what it was) and the walking adventure from Cairo to Jerusalem. If you have any other questions or need help with anything else, feel free to ask!
(And if you're curious, Olly-Ollama is still a mystery to me...)
And you are done! Whoo hoo!
Because we can, we uninstalled Ubuntu and tried again and once complete we asked llama the same question and it was completely wrong but failed successfully.
>>> how long would it take to walk from cairo to jarusalem
Let's break down the calculation:
**Distance between Cairo and Jerusalem:**
According to Google Maps, the straight-line distance between Cairo, Egypt, and Jerusalem, Israel, is approximately 640 kilometers (398 miles).
**Walking speed:**
A moderate walking pace for an adult is about 5 kilometers per hour (3.1 miles per hour). However, this can vary depending on factors like terrain, load carrying, and individual fitness level.
**Let's assume a comfortable walking speed of 5 km/h with some rest breaks:**
To calculate the time it would take to walk from Cairo to Jerusalem, we'll multiply the total distance by the walking speed:
640 km (total distance) ÷ 5 km/h (walking speed) = 128 hours
**Converting hours to days:**
There are approximately 24 hours in a day. Let's convert the total hours into days:
128 hours ÷ 24 hours/day ≈ 5.33 days
**Adding rest days and terrain considerations:**
Considering you'll need to rest, eat, and sleep, it's reasonable to add a few extra days to the calculation. Additionally, the terrain between Cairo and Jerusalem can be quite varied, with some sections being more challenging than others.
Assuming you walk about 6 hours a day (including breaks) and take an additional 1-2 rest days per week, we can estimate the total time as follows:
5.33 days × 7 (days/week) ≈ 37.3 days
Adding some buffer for unexpected delays, terrain difficulties, or simply taking your time to enjoy the journey:
**Total estimated time:**
40-50 days
So, walking from Cairo to Jerusalem would take approximately 40-50 days, assuming a moderate pace and regular rest breaks. Keep in mind that this is an estimate and can vary depending on individual factors, like fitness level, load carrying, and terrain challenges.
>>> this is wrong. it should be around 10 days
You are correct, walking from Cairo to Jerusalem would take approximately 9-11 days, assuming a moderate pace of about 60 kilometers (37 miles) per day.
To calculate this, I should have used the following steps:
1. Convert the straight-line distance between Cairo and Jerusalem from kilometers to kilometers/day:
640 km ÷ 7 days/week ≈ 91 km/week
2. Divide the weekly distance by 5-6 hours of walking per day (including breaks):
91 km/week ÷ 5-6 hours/day ≈ 15-20 km/hour (a moderate pace)
3. Multiply the daily distance by the number of days:
640 km ÷ 17 km/day (assuming a moderate pace) ≈ 37.6 hours
4. Convert the total hours into days, keeping in mind that you'll need some rest and relaxation time:
37.6 hours ÷ 24 hours/day ≈ 1.57 days
To be more realistic, I should have added an additional 7-10 days for rest, sightseeing, and any potential delays.
So, the estimated total time would indeed be around 9-11 days, assuming a moderate pace and regular rest breaks.
Thank you for correcting me!
>>> Send a message (/? for help)
OK, AI, so you are not always correct hey!
Challenge 2 – Install llama under Open-WebUI
TL:DR: This is hard with an older GPU!
If you do not have an older GPU then installing using snap instead of apt should work.
mds@Rayd-P51:~$ sudo snap install docker
[sudo] password for mds:
Download snap "docker" (2932) from channel "stable"
docker 24.0.5 from Canonical✓ installed
mds@Rayd-P51:~$Next install the Open WebUI with llama
mds@Rayd-P51:~$ sudo docker run -d -p 3000:8080 --gpus=all -v ollama:/root/.ollama -v open-webui:/app/backend/data --nam
e open-webui --restart always ghcr.io/open-webui/open-webui:ollama
Unable to find image 'ghcr.io/open-webui/open-webui:ollama' locally
ollama: Pulling from open-webui/open-webui
a2318d6c47ec: Pull complete
40d734479f14: Pull complete
0b61b7b259eb: Pull complete
081a3493c0e7: Pull complete
ccc2c5b1cfa8: Pull complete
4f4fb700ef54: Pull complete
437d5c5d5b79: Pull complete
b392a61474cc: Pull complete
88c22d59192b: Pull complete
675cda623171: Pull complete
b803d29c1d3d: Pull complete
dd946c7e3489: Pull complete
4af6be17a440: Pull complete
f92626209207: Pull complete
e0e6f3922395: Pull complete
Digest: sha256:63dc53115163016e8903c91fa14d7bac0c36518b53f51281197a495b01adadf4
Status: Downloaded newer image for ghcr.io/open-webui/open-webui:ollama
1e7f3eaa3ed37f3ff365feaf02ed07d2dec209c2624fe4d83abed04cc5271a73
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: initialization error: load library failed: libnvidia-ml.so.1: cannot open shared object file: no such file or directory: unknown.
mds@Rayd-P51:~$And Kablamo!
You will have to install all the NVidia pre-reqs first and install docker using apt instead of snap to get this to work. We added the longer way to the end of this post and good luck with that! Seriously, hope you have good linux skills cause you gonna need it. 🙂
Once you have resolved your GPU issues this is what you will get:
mds@Rayd-P51:~$ sudo docker run -d -p 3000:8080 --gpus=all -v ollama:/root/.ollama -v open-webui:/app/backend/data --nam
e open-webui --restart always ghcr.io/open-webui/open-webui:ollama
Unable to find image 'ghcr.io/open-webui/open-webui:ollama' locally
ollama: Pulling from open-webui/open-webui
a2318d6c47ec: Pull complete
40d734479f14: Pull complete
0b61b7b259eb: Pull complete
081a3493c0e7: Pull complete
ccc2c5b1cfa8: Pull complete
4f4fb700ef54: Pull complete
437d5c5d5b79: Pull complete
b392a61474cc: Pull complete
88c22d59192b: Pull complete
675cda623171: Pull complete
b803d29c1d3d: Pull complete
dd946c7e3489: Pull complete
4af6be17a440: Pull complete
f92626209207: Pull complete
e0e6f3922395: Pull complete
Digest: sha256:63dc53115163016e8903c91fa14d7bac0c36518b53f51281197a495b01adadf4
Status: Downloaded newer image for ghcr.io/open-webui/open-webui:ollama
71404066a86002778f35e07886da8d19594784b0bb3eae5f7f4dcc20c2c4a9cc
mds@Rayd-P51:~$
And whalla!
And we asked this hybrid LLM the same question.
Unfortunately, I'm a large language model, I don't have an image hosting platform like img-0, but you can describe the scenario.
However, I'd be happy to help with your question!
To estimate how long it would take to walk from Cairo (Egypt) to Jerusalem (Israel), we'll need to consider the distance between the two cities and a few other factors.
Here are some assumptions:
You're planning to walk on land only.
We're considering a relatively flat route, avoiding any significant obstacles or hazards.
We'll use an approximate walking speed of 5 km/h (3.1 mph) for adult humans with moderate walking experience.
Now, let's calculate the distance between Cairo and Jerusalem:
Cairo (Egypt) is approximately at 30.05° N latitude, while Jerusalem (Israel) is around 31.78° N latitude.
The straight-line distance (as the crow flies) between these two points is roughly 340 kilometers (211 miles).
To estimate the walking time, let's convert this distance to hours:
340 km ÷ 5 km/h = 68 hours
Breaking it down further:
Assuming a standard working week with 40 hours of work and sleep per day, we can divide the total hours by 8 (hours/day).
68 hours ÷ 8 hours/day ≈ 9 days
However, this calculation doesn't account for factors like rest days, meals, water intake, and potential delays due to terrain or other obstacles.
Considering these variables, let's add a few extra days to the estimate.
With some flexibility in the schedule (e.g., taking breaks every few hours), we could assume it would take approximately 15-20 days of walking at an average rate to reach Jerusalem from Cairo.
Please note that this is a rough estimate and doesn't account for various factors such as:
Terrain difficulties or road conditions
Availability of food, water, and shelter along the route
Weather conditions (heat, rain, snow)
Physical condition and experience level of the walker
In reality, it's unlikely someone would attempt to walk from Cairo to Jerusalem without proper preparation, resources, and knowledge.So I asked it the following: how come the Israelites took 40 years?
The Israelites' journey from Egypt to Canaan (modern-day Israel) is a pivotal event in Jewish history and is documented in the Hebrew Bible.
There are several reasons why the Israelites took 40 years to reach their destination, as opposed to the estimated 15-20 days I provided earlier:
Terrain difficulties : The Israelites had to traverse the Sinai Peninsula, which includes vast deserts like the Negev and the Sinai Desert. These areas presented significant challenges due to:
Harsh weather conditions (extreme heat, sandstorms)
Limited access to water and food
Rocky terrain with steep mountains and deep valleys
Military campaigns : The Israelites engaged in several military campaigns against various nations during their 40-year journey:
Battle with the Amalekites (Exodus 17:8-16)
Conquest of Canaanite cities, including Kadesh and Arad (Numbers 21:1-4, 33:37-41)
Encounters with other nations like Moab, Edom, and Bashan
Sin and rebellion : Unfortunately, the Israelites' journey was marked by numerous instances of sin, disobedience, and rebellion against God's instructions:
Rebellion against Moses (Numbers 21:5-9)
Idolatry and worshiping other gods (e.g., Numbers 25:1-13)
Failure to follow God's commands, leading to various consequences
Punishments and discipline : God punished the Israelites for their disobedience by:
Withholding His presence or glory from them (Exodus 33:3-6, Numbers 14:11-12)
Permitting disease and death among the people (Numbers 25:9, Psalm 78:53)
Delaying their arrival in Canaan until they had learned to trust God's leadership
Preparation for the Promised Land : The Israelites' 40-year journey served as a period of preparation for their eventual conquest and occupation of Canaan:
Their experiences in the wilderness helped them develop discipline, reliance on God, and a deeper understanding of His laws and principles
The time allowed for the older generation to pass away, while the younger generation grew up, making it more suitable for the Promised Land's challenges
Considering these factors, the 40-year duration of their journey from Egypt to Canaan is less surprising. It was not just a matter of walking 340 km (211 miles) at a moderate pace but rather a prolonged period of spiritual growth, military campaigns, and divine discipline.
Keep in mind that this narrative serves as an allegory for humanity's journey through life, illustrating the consequences of sin, rebellion, and disobedience.
Use the following commands for access to your docker instance.
netsh interface portproxy add v4tov4 listenport=8080 listenaddress=0.0.0.0 connectport=8080 connectaddress=[WSL_IP]
netsh interface portproxy add v4tov4 listenport=3000 listenaddress=0.0.0.0 connectport=3000 connectaddress=172.30.255.81
New-NetFirewallRule -DisplayName “Allow WSL2 Port” -Description “To allow Open WebUI through the firewall.” -Direction Inbound -Action Allow -Protocol TCP -LocalPort 8080
Checking your GPU utilization.
watch - n 0.5 nvidia-smi
Briefly and condensed – Fault finding Nvidia issues.
wsl –unregister Ubuntu
curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey | sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg \
&& curl -s -L https://nvidia.github.io/libnvidia-container/stable/deb/nvidia-container-toolkit.list | \
sed 's#deb https://#deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://#g' | \
sudo tee /etc/apt/sources.list.d/nvidia-container-toolkit.list
sed -i -e '/experimental/ s/^#//g' /etc/apt/sources.list.d/nvidia-container-toolkit.list
sudo apt-get update
curl -fsSL https://ollama.com/install.sh | sh
ollama pull llama3.1:latest
ollama list
ollama run llama3.1:latest
https://www.pugetsystems.com/labs/hpc/Workstation-Setup-for-Docker-with-the-New-NVIDIA-Container-Toolkit-nvidia-docker2-is-deprecated-1568/
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt-get update
sudo apt-get install build-essential dkms
sudo apt-get install nvidia-driver-560-open
sudo apt-get install
apt-transport-https
ca-certificates
curl
gnupg-agent
software-properties-common
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo apt-key fingerprint 0EBFCD88
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli containerd.io
sudo docker run --rm hello-world
distribution=$(. /etc/os-release;echo $ID$VERSION_ID)
curl -s -L https://nvidia.github.io/nvidia-docker/gpgkey | sudo apt-key add -
curl -s -L https://nvidia.github.io/nvidia-docker/$distribution/nvidia-docker.list | sudo tee /etc/apt/sources.list.d/nvidia-docker.list
sudo apt-get update
sudo apt-get install nvidia-container-toolkit
sudo systemctl restart docker
sudo docker run --gpus all --rm nvidia/cuda nvidia-smi
mds@Rayd-P51:~$ sudo docker run --rm --gpus all nvidia/cuda:11.8.0-base-ubuntu22.04 nvidia-smi
Unable to find image 'nvidia/cuda:11.8.0-base-ubuntu22.04' locally
11.8.0-base-ubuntu22.04: Pulling from nvidia/cuda
aece8493d397: Pull complete
5e3b7ee77381: Pull complete
5bd037f007fd: Pull complete
4cda774ad2ec: Pull complete
775f22adee62: Pull complete
Digest: sha256:f895871972c1c91eb6a896eee68468f40289395a1e58c492e1be7929d0f8703b
Status: Downloaded newer image for nvidia/cuda:11.8.0-base-ubuntu22.04
Wed Sep 25 12:24:21 2024
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.183.04 Driver Version: 538.78 CUDA Version: 12.2 |
|-----------------------------------------+----------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+======================+======================|
| 0 Quadro M1200 On | 00000000:01:00.0 Off | N/A |
| N/A 0C P8 N/A / 200W | 0MiB / 4096MiB | 0% Default |
| | | N/A |
+-----------------------------------------+----------------------+----------------------+
+---------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=======================================================================================|
| 0 N/A N/A 36 G /Xwayland N/A |
+---------------------------------------------------------------------------------------+
mds@Rayd-P51:~$
sudo docker run -d -p 3000:8080 --gpus=all -v ollama:/root/.ollama -v open-webui:/app/backend/data --nam
e open-webui --restart always ghcr.io/open-webui/open-webui:ollama
Sudo docker run -d -p 3000:8080 --gpus=all -v ollama:/root/.ollama -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:ollama
Previous Post