From 5757a85b1e6a08e45a75317d077c13c5f15053c3 Mon Sep 17 00:00:00 2001 From: GitLab CI Date: Sun, 12 Oct 2025 18:54:50 +0000 Subject: [PATCH] chore: Regenerate all playbooks --- nvidia/dgx-dashboard/README.md | 2 +- nvidia/jax/README.md | 3 +-- nvidia/multi-agent-chatbot/README.md | 2 +- nvidia/nvfp4-quantization/README.md | 6 ++---- nvidia/open-webui/README.md | 4 ++-- nvidia/pytorch-fine-tune/README.md | 6 ++---- nvidia/speculative-decoding/README.md | 2 +- nvidia/trt-llm/README.md | 5 ++--- nvidia/txt2kg/README.md | 6 +++--- nvidia/vlm-finetuning/README.md | 6 ++---- nvidia/vss/README.md | 6 +----- 11 files changed, 18 insertions(+), 30 deletions(-) diff --git a/nvidia/dgx-dashboard/README.md b/nvidia/dgx-dashboard/README.md index dd7a5a6..f2c3b6a 100644 --- a/nvidia/dgx-dashboard/README.md +++ b/nvidia/dgx-dashboard/README.md @@ -222,7 +222,7 @@ Now that you have DGX Dashboard configured, you can: | Symptom | Cause | Fix | |---------|-------|-----| -| User can't run updates | User not in sudo group | Add user to sudo group: `sudo usermod -aG sudo ` | +| User can't run updates | User not in sudo group | Add user to sudo group: `sudo usermod -aG sudo `; then run `newgrp docker`| | JupyterLab won't start | Issue with current virtual environment | Change the working directory in the JupyterLab panel and start a new instance | | SSH tunnel connection refused | Incorrect IP or port | Verify Spark device IP and ensure SSH service is running | | GPU not visible in monitoring | Driver issues | Check GPU status with `nvidia-smi` | diff --git a/nvidia/jax/README.md b/nvidia/jax/README.md index acbb03b..1d206a3 100644 --- a/nvidia/jax/README.md +++ b/nvidia/jax/README.md @@ -83,12 +83,11 @@ uname -m docker run --gpus all --rm nvcr.io/nvidia/cuda:13.0.1-runtime-ubuntu24.04 nvidia-smi ``` -If the `docker` command fails with a permission error, you can either run the command with `sudo`, or add yourself to the `docker` group to use `docker` without `sudo`. +If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group, so that you don't need to use the command with sudo . ```bash sudo usermod -aG docker $USER newgrp docker -sudo systemctl restart docker ``` ## Step 2. Clone the playbook repository diff --git a/nvidia/multi-agent-chatbot/README.md b/nvidia/multi-agent-chatbot/README.md index bb02444..7fadc93 100644 --- a/nvidia/multi-agent-chatbot/README.md +++ b/nvidia/multi-agent-chatbot/README.md @@ -61,7 +61,7 @@ Open a new terminal and test Docker access. In the terminal, run: docker ps ``` -If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group, so that you don't need to use the command with sudo . +If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group so that you don't need to run the command with sudo . ```bash sudo usermod -aG docker $USER diff --git a/nvidia/nvfp4-quantization/README.md b/nvidia/nvfp4-quantization/README.md index 16cc803..c500e0c 100644 --- a/nvidia/nvfp4-quantization/README.md +++ b/nvidia/nvfp4-quantization/README.md @@ -80,15 +80,13 @@ Open a new terminal and test Docker access. In the terminal, run: docker ps ``` -If you see a permission denied error (something like `permission denied while trying to connect to the Docker daemon socket`), add your user to the docker group: +If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group so that you don't need to run the command with sudo . ```bash sudo usermod -aG docker $USER +newgrp docker ``` -> **Warning**: After running usermod, you must log out and log back in to start a new -> session with updated group permissions. - ## Step 2. Prepare the environment Create a local output directory where the quantized model files will be stored. This directory will be mounted into the container to persist results after the container exits. diff --git a/nvidia/open-webui/README.md b/nvidia/open-webui/README.md index 0d7fa71..3626ca0 100644 --- a/nvidia/open-webui/README.md +++ b/nvidia/open-webui/README.md @@ -56,7 +56,7 @@ Open a new terminal and test Docker access. In the terminal, run: docker ps ``` -If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group, so that you don't need to use the command with sudo . +If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group so that you don't need to run the command with sudo . ```bash sudo usermod -aG docker $USER @@ -177,7 +177,7 @@ Open the Terminal app from NVIDIA Sync to start an interactive SSH session and t docker ps ``` -If you see a permission denied error (something like `permission denied while trying to connect to the Docker daemon socket`), add your user to the docker group: +If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group so that you don't need to run the command with sudo . ```bash sudo usermod -aG docker $USER diff --git a/nvidia/pytorch-fine-tune/README.md b/nvidia/pytorch-fine-tune/README.md index 5b46e4d..b08700f 100644 --- a/nvidia/pytorch-fine-tune/README.md +++ b/nvidia/pytorch-fine-tune/README.md @@ -53,15 +53,13 @@ Open a new terminal and test Docker access. In the terminal, run: docker ps ``` -If you see a permission denied error (something like `permission denied while trying to connect to the Docker daemon socket`), add your user to the docker group: +If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group so that you don't need to run the command with sudo . ```bash sudo usermod -aG docker $USER +newgrp docker ``` -> **Warning**: After running usermod, you must log out and log back in to start a new -> session with updated group permissions. - ## Step 2. Pull the latest Pytorch container ```bash diff --git a/nvidia/speculative-decoding/README.md b/nvidia/speculative-decoding/README.md index 0a8d16e..b9db713 100644 --- a/nvidia/speculative-decoding/README.md +++ b/nvidia/speculative-decoding/README.md @@ -68,7 +68,7 @@ Open a new terminal and test Docker access. In the terminal, run: docker ps ``` -If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group, so that you don't need to use the command with sudo . +If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group so that you don't need to run the command with sudo . ```bash sudo usermod -aG docker $USER diff --git a/nvidia/trt-llm/README.md b/nvidia/trt-llm/README.md index d61ad23..86c4375 100644 --- a/nvidia/trt-llm/README.md +++ b/nvidia/trt-llm/README.md @@ -130,7 +130,7 @@ Open a new terminal and test Docker access. In the terminal, run: docker ps ``` -If you see a permission denied error (something like `permission denied while trying to connect to the Docker daemon socket`), add your user to the docker group: +If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group so that you don't need to run the command with sudo . ```bash sudo usermod -aG docker $USER @@ -429,13 +429,12 @@ Open a new terminal and test Docker access. In the terminal, run: docker ps ``` -If you see a permission denied error (something like `permission denied while trying to connect to the Docker daemon socket`), add your user to the docker group: +If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group so that you don't need to run the command with sudo . ```bash sudo usermod -aG docker $USER newgrp docker ``` - ### Step 3. Install NVIDIA Container Toolkit & setup Docker environment Ensure the NVIDIA drivers and the NVIDIA Container Toolkit are installed on each node (both manager and workers) that will provide GPU resources. This package enables Docker containers to access the host's GPU hardware. Ensure you complete the [installation steps](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html), including the [Docker configuration](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html#configuring-docker) for NVIDIA Container Toolkit. diff --git a/nvidia/txt2kg/README.md b/nvidia/txt2kg/README.md index 363a6be..0696122 100644 --- a/nvidia/txt2kg/README.md +++ b/nvidia/txt2kg/README.md @@ -43,16 +43,16 @@ The setup includes: ## Time & risk -⏱️ **Duration**: +**Duration**: - 2-3 minutes for initial setup and container deployment - 5-10 minutes for Ollama model download (depending on model size) - Immediate document processing and knowledge graph generation -⚠️ **Risks**: +**Risks**: - GPU memory requirements depend on chosen Ollama model size - Document processing time scales with document size and complexity -↩️ **Rollback**: Stop and remove Docker containers, delete downloaded models if needed +**Rollback**: Stop and remove Docker containers, delete downloaded models if needed ## Instructions diff --git a/nvidia/vlm-finetuning/README.md b/nvidia/vlm-finetuning/README.md index 942a874..7649744 100644 --- a/nvidia/vlm-finetuning/README.md +++ b/nvidia/vlm-finetuning/README.md @@ -67,15 +67,13 @@ Open a new terminal and test Docker access. In the terminal, run: docker ps ``` -If you see a permission denied error (something like `permission denied while trying to connect to the Docker daemon socket`), add your user to the docker group: +If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group so that you don't need to run the command with sudo . ```bash sudo usermod -aG docker $USER +newgrp docker ``` -> **Warning**: After running usermod, you must log out and log back in to start a new -> session with updated group permissions. - ## Step 2. Clone the repository In a terminal, clone the repository and navigate to the VLM fine-tuning directory. diff --git a/nvidia/vss/README.md b/nvidia/vss/README.md index 676d86c..def985d 100644 --- a/nvidia/vss/README.md +++ b/nvidia/vss/README.md @@ -81,17 +81,13 @@ Open a new terminal and test Docker access. In the terminal, run: docker ps ``` -If you see a permission denied error (something like `permission denied while trying to connect to the Docker daemon socket`), add your user to the docker group: +If you see a permission denied error (something like permission denied while trying to connect to the Docker daemon socket), add your user to the docker group so that you don't need to run the command with sudo . ```bash sudo usermod -aG docker $USER newgrp docker ``` -> **Warning**: After running usermod, you must log out and log back in to start a new -> session with updated group permissions, or in rare cases restart their spark for the -> changes to take effect. - Additionally, configure Docker so that it can use the NVIDIA Container Runtime.