Run ROCm-RAG in an interactive session

Run ROCm-RAG in an interactive session#

2026-04-28

5 min read time

Applies to Linux

You can run the ROCm-RAG extraction and retrieval pipelines in a Docker container in an interactive session to explore and debug the container manually. You can scrape and extract data to the Weaviate vector database (the AI-native vector database used by ROCm-RAG), then retrieve that data with the RAG retrieval pipeline.

Start the container with a bash session#

Open your terminal and use the following command to start the container:

docker run --cap-add=SYS_PTRACE --ipc=host --privileged=true \
        --shm-size=128GB --network=host --device=/dev/kfd \
        --device=/dev/dri --group-add video -it \
rocm/rocm-rag:rocm-rag-1.0.0-rocm6.4.1-ubuntu22.04

Once the container is running, you can start using the ROCm-RAG extraction and retrieval pipelines.

Run the extraction pipeline#

Run the extraction pipeline to gather data. By default, the scraper will scrape all blog pages starting from the ROCm Blogs home page.

Limit the scope of scraping (optional)#

You can limit the scope of scraping by setting the following environment variables. Here’s an example of scraping a single blog page about ROCm-DS, so the extraction pipeline builds the knowledge base only from this blog page:

export ROCM_RAG_START_URLS="https://rocm.blogs.amd.com/software-tools-optimization/introducing-rocm-ds-revolutionizing-data-processing-with-amd-instinct-gpus/README.html"
export ROCM_RAG_SET_MAX_NUM_PAGES=True
export ROCM_RAG_MAX_NUM_PAGES=1

Start the extraction pipeline#

By default, the page hash database is under /rag-workspace/rocm-rag/hash, and the Weaviate persistent data is under /rag-workspace/rocm-rag/data. Ensure you mount these directories to your host directories so that you can reuse the extracted data:

cd /rag-workspace/rocm-rag/scripts
bash run-extraction-tmux.sh # OR bash run-extraction.sh

You can switch to a different bash terminal window with tmux select-window -t <window ID>.

The logs for extraction components can be found under /rag-workspace/rocm-rag/logs.

The extraction script crawls, scrapes, chunks, indexes, and saves the content to the database for future use. After scraping and indexing, you’ll see the message All URLs found: <your starting URL>.

Verify the extraction#

Once finished, you can run a quick test to retrieve the content from the Weaviate vector database:

cd /rag-workspace/rocm-rag/tests/examples
python weaviate_client_example.py

This pulls and prints out all scraped and indexed chunks from the starting URL.

Run the retrieval pipeline#

Use the following command to start the retrieval pipelines to get the extracted data from the Weaviate database:

cd /rag-workspace/rocm-rag/scripts
bash run-retrieval-tmux.sh # OR bash run-retrieval.sh

You can switch to a different bash terminal window with tmux select-window -t <window ID>.

The retrieval component logs are under /rag-workspace/rocm-rag/logs.

After the retrieval process completes, this message is returned in example_llm_retrieval.log and embedder_retrieval.log:

INFO:     Application startup complete.

Configure the SSL certificate and enable HTTPS#

Access to the Automatic Speech Recognition feature requires microphone permissions. Certain web browsers enforce a security policy requiring websites to be served via HTTPS (Hypertext Transfer Protocol Secure) to access the microphone. You can configure HTTPS using a self-signed certificate for testing purposes only.

Warning

Don’t use this approach in production environments. For production deployments, configure a valid domain name and obtain an SSL/TLS certificate from a trusted certificate authority.

  1. Get the machine IP.

    # Get private IP inside LAN
apt install net-tools && ifconfig

  2. Create a self-signed certificate with the SAN included.

    After obtaining the IP address, create a self-signed SSL certificate valid for 365 days saved to /etc/nginx/ssl/selfsigned.crt. It’s saved together with a new RSA private key in /etc/nginx/ssl/selfsigned.key:

    mkdir -p /etc/nginx/ssl
openssl req -x509 -nodes -days 365 -newkey rsa:2048 \
  -keyout /etc/nginx/ssl/selfsigned.key \
  -out /etc/nginx/ssl/selfsigned.crt \
  -subj "/C=US/ST=Local/L=Local/O=Local/CN=<your machine IP>" \
  -addext "subjectAltName=IP:<your machine IP>"

  3. Start nginx (if it isn’t already running).

    nginx

  4. Configure nginx to enable HTTPS.

    cat <<'EOF' >> /etc/nginx/sites-available/default
server {
    listen 443 ssl;
    listen [::]:443 ssl;
    server_name <your IP address>;  # Accept any hostname

    ssl_certificate     /etc/nginx/ssl/selfsigned.crt;
    ssl_certificate_key /etc/nginx/ssl/selfsigned.key;

    location / {
        proxy_pass http://localhost:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header Accept-Encoding "";
        proxy_set_header X-Forwarded-Scheme $scheme;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

        # Websockets
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        ##
        # Disable buffering for the streaming responses (SSE)
        chunked_transfer_encoding off;
        proxy_buffering off;
        proxy_cache off;
        ##
        # Connections Timeouts (1hr)
        keepalive_timeout 3600;
        proxy_connect_timeout 3600;
        proxy_read_timeout 3600;
        proxy_send_timeout 3600;
        ##
    }
}
EOF

  5. Reload nginx.

    nginx -s reload

  6. Test and reload the nginx configuration.

    -t checks for syntax errors in the config files, and -s reloads the configuration without stopping the service:

    nginx -t
nginx -s reload
Contents