nvidia-docker VS text-generation-webui

Nvidia Docker on GitHub

Here's where I found discussion regarding this https://github.com/NVIDIA/nvidia-docker/issues/1671

I found the Faq, looks like Windows isn't supported which might indicate why I had this problem earlier. I might need to dual boot my machine if it won't work with WSL which I don't see mentioned in either page. WSL Cuda instructions found this I'll give it a try.

Arc has linux kernel support from 6.0, been using an A770 with tdarr for a few months. Super solid and no issues like the nvidia docker toolkit just losing the GPU. The workaround doesn't hold for long - https://github.com/NVIDIA/nvidia-docker/issues/1730 It is one of the reasons I went with Intel over waiting for a low end 40 series. The other was I that basically stole it for $199. So far Plex is the only thing that doesn't work with Arc and all the HW transcoding falls on the iGPU. Knowing how they prioritize things nobody wants, Arc support and AV1 transcoding will be added when 16th gen Intel CPUs are released.

I use ubuntu with wsl2 under windows 11. I want to learn how to get GPU-accelerated computing working. My ASUS laptop has a NVIDIA graphics card as well as a built in Intel. Please ask me any needed questions and then tell me the steps I need to get this working? SOFTWARE DEVELOPER Thanks for sharing that information. Can you please confirm if you have already installed NVIDIA drivers on your Windows 11 system? If not, you'll need to install the appropriate NVIDIA drivers for your GPU in order to enable GPU acceleration. Additionally, what is your end goal is with GPU accelerated computing? yes I have the NVIDIA control panel installed. SOFTWARE DEVELOPER Great. To enable GPU acceleration in WSL2, you'll need to follow these steps: First, confirm you are running Windows 11 build 20145 or later, and have WSL2 installed and configured to use Ubuntu. Download the NVIDIA Linux driver for your GPU from the official NVIDIA Linux download page https://www.nvidia.com/Download/index.aspx. Install the latest NVIDIA driver, including the NVIDIA Docker plugin. You can follow instructions on the NVIDIA Docker plugin GitHub page (https://github.com/NVIDIA/nvidia-docker). Install the CUDA toolkit and cuDNN library. Once you've installed the NVIDIA driver successfully, you can download the CUDA toolkit and cuDNN library (if applicable) from the official NVIDIA CUDA download page https://developer.nvidia.com/cuda-downloads. Install the NVIDIA Container Toolkit. NVIDIA Container Toolkit is a nifty package that provides a set of tools for GPU-accelerated container deployments. You can find installation instructions and a getting started guide on the NVIDIA Container Toolkit GitHub page https://github.com/NVIDIA/nvidia-docker. Test the installation by running a TensorFlow or PyTorch script that uses the GPU for accelerated computing. Check if the GPU is recognized and being used in the output of the script. Once you've successfully followed these steps, you should have GPU-accelerated computing environments in WSL2. Hope that helps! Let me know if you have any other questions. yes to question #1. On #2, do I download the Game Ready driver or the Studio Driver. I don't play games as I'm a software devevloper but want accelerated graphics for development or data science purposes. SOFTWARE DEVELOPER Great to hear that you have WSL2 set up on your system. Regarding your question, you should download the Studio Driver version, as it's optimized for professional workloads, including data science and software development. The Game Ready version is optimized for gaming and might not always provide the best performance for non-gaming workloads. Once you have downloaded the Studio Driver for your GPU, follow the instructions provided by the driver installer to complete the installation process. Let me know if you have any further questions! Would you clarify #3? Is the NVIDIA Docker plugin included with the NVIDIA driver install? Or is it a separate install. I have Docker for Windows installed and working in WSL2. SOFTWARE DEVELOPER Sure, I'd be happy to clarify. The NVIDIA Docker plugin is an additional package that needs to be installed separately from the NVIDIA drivers. The plugin provides a convenient way for creating and running GPU-accelerated Docker containers in your system. To install the NVIDIA Docker plugin, follow the instructions on the NVIDIA Docker plugin GitHub page (https://github.com/NVIDIA/nvidia-docker). Note that the plugin is only compatible with Docker CE (Community Edition) or Docker EE (Enterprise Edition) on Linux-based systems, and does not work on Docker for Windows. Once you've installed the plugin, you can use it to run GPU-accelerated containers with Docker. It's worth noting that the NVIDIA Docker plugin requires access to your host system's NVIDIA GPU, so you'll need to ensure that your GPU has been correctly installed and recognized by your system. Hope that answers your question. Let me know if you have any additional questions!

Im trying to determine how to troubleshoot & resolve the HW transcoding, but based on my testing Im assuming its some change to the NVIDIA toolkit https://github.com/NVIDIA/nvidia-docker

NVIDIA Container Toolkit

So I am in the initial planning stages of setting up a new unraid server. Looking at picking up an SC846 24bay 4u chassis. I've got a Gigabyte Aorus mb with an AMD 5950x, 32gb of ddr4 (adding more as needed) and an nvidia 3070ti. I plan on getting an LSI 8i for the drives and leaves room for expansion server plans. My goal is to have plex setup via docker and utilize the gpu transcoding to offload the cpu work. I also want to setup vms or a vm server to essentially also have a "gaming server" mainly for me and the kids. This means down the road I would be adding another GPU to split up with other users. Im trying to allow for a max of 4 people while also still allowing plex to transcode as needed. Now I know there's other ways to do this but I dont feel like splitting this up into multiple systems unless I have to. So really just trying to see if this might be possible. My worry is that in order to make the gpu available to the plex docker I have to setup an nvidia container. https://github.com/NVIDIA/nvidia-docker

Some of the tools offer a path to doing tool use (fetching URLs and doing things with them) or RAG (searching your documents). I think Oobabooga https://github.com/oobabooga/text-generation-webui offers the latter through plugins.

Our tool, https://github.com/transformerlab/transformerlab-app also supports the latter (document search) using local llms.

You can use webui https://github.com/oobabooga/text-generation-webui

Once you get a version up and running I make a copy before I update it as several times updates have broken my working version and caused headaches.

a decent explanation of parameters outside of reading archive papers: https://github.com/oobabooga/text-generation-webui/wiki/03-%...

a news ai website:

The other answers are recommending paths which give you #1. less control and #2. projects with smaller eco-systems.

If you want a truly general purpose front-end for LLMs, the only good solution right now is oobabooga: https://github.com/oobabooga/text-generation-webui

All other alternatives have only small fractions of the features that oobabooga supports. All other alternatives only support a fraction of the LLM backends that oobabooga supports, etc.

The example waifu in text-generation-webui is good enough for me.

https://github.com/oobabooga/text-generation-webui/blob/main...

> Downloading text-generation-webui takes a minute, let's you use any model and get going.

What you're missing here is you're already in this area deep enough to know what ooogoababagababa text-generation-webui is. Let's back out to the "average Windows desktop user" level. Assuming they even know how to find it:

1) Go to https://github.com/oobabooga/text-generation-webui?tab=readm...

2) See a bunch of instructions opening a terminal window and running random batch/powershell scripts. Powershell, etc will likely prompt you with a scary warning. Then you start wondering who ooobabagagagaba is...

3) Assuming you get this far (many users won't even get to step 1) you're greeted with a web interface[0] FILLED to the brim with technical jargon and extremely overwhelming options just to get a model loaded, which is another mind warp because you get to try to select between a bunch of random models with no clear meaning and non-sensical/joke sounding names from someone called "TheBloke". Ok...

Let's say you somehow braved this gauntlet and get this far now you get to chat with it. Ok, what about my local documents? text-generation-webui itself has nothing for that. Repeat this process over the 10 random open source projects from a bunch of names you've never heard of in an attempt to accomplish that.

This is "I saw this thing from Nvidia explode all over media, twitter, youtube, etc. I downloaded it from Nvidia, double-clicked, pointed it at a folder with documents, and it works".

That's the difference and it's very significant.

[0] - https://raw.githubusercontent.com/oobabooga/screenshots/main...

Maybe a copout answer, but setting up a local LLM on my development machine has been invaluable. I use Deep Seek Coder 6.7 [0] and Oobabooga's UI [1]. It helps me solve simple problems and find bugs, while still leaving the larger architecture decisions to me.

[0] https://huggingface.co/deepseek-ai/deepseek-coder-6.7b-instr...

[1] https://github.com/oobabooga/text-generation-webui

You can download it and run it with [this](https://github.com/oobabooga/text-generation-webui). There's an API mode that you could leverage from your VS Code extension.

Same question here. Ollama is fantastic as it makes it very easy to run models locally, But if you already have a lot of code that processes OpenAI API responses (with retry, streaming, async, caching etc), it would be nice to be able to simply switch the API client to Ollama, without having to have a whole other branch of code that handles Alama API responses. One way to do an easy switch is using the litellm library as a go-between but it’s not ideal (and I also recently found issues with their chat formatting for mistral models).

For an OpenAI compatible API my current favorite method is to spin up models using oobabooga TGW. Your OpenAI API code then works seamlessly by simply switching out the api_base to the ooba endpoint. Regarding chat formatting, even ooba’s Mistral formatting has issues[1] so I am doing my own in Langroid using HuggingFace tokenizer.apply_chat_template [2]

[1] https://github.com/oobabooga/text-generation-webui/issues/53...

[2] https://github.com/langroid/langroid/blob/main/langroid/lang...

Related question - I assume ollama auto detects and applies the right chat formatting template for a model?