|
| 1 | +--- |
| 2 | +title: 'Deploying NVIDIA NIM' |
| 3 | +description: 'Deploy NVIDIA NIM microservices on CCluster through General Inference' |
| 4 | +icon: 'box-open-full' |
| 5 | +--- |
| 6 | + |
| 7 | +[NVIDIA NIM](https://developer.nvidia.com/nim) microservices are self-contained containers that bundle a model-optimized inference engine and download model weights automatically at startup, exposing an OpenAI-compatible API. NIM is not a pre-configured recipe on the [General Inference](/apps/inference) page — enter the image manually with the settings below. |
| 8 | + |
| 9 | +## Find a NIM image |
| 10 | + |
| 11 | +NIM images are hosted on `nvcr.io`. Browse the catalog at [build.nvidia.com](https://build.nvidia.com/explore/discover) and copy the image path from the model's **Deploy** tab. The catalog shows the image and tag joined with a colon (e.g. `nvcr.io/nim/meta/llama-3.1-8b-instruct:latest`) — on CCluster, split them into the **Add or Select Image** and **Container Tag** fields: |
| 12 | + |
| 13 | +| Image | Tag | |
| 14 | +|---|---| |
| 15 | +| `nvcr.io/nim/deepseek-ai/deepseek-r1-distill-qwen-32b` | `latest` | |
| 16 | +| `nvcr.io/nim/meta/llama-3.1-8b-instruct` | `latest` | |
| 17 | + |
| 18 | +You also need an [NGC API Key](https://ngc.nvidia.com) — it is used both to pull the image and to download model weights. |
| 19 | + |
| 20 | +## Configure the deployment |
| 21 | + |
| 22 | +From the **General Inference** deployment page, every NIM uses the same configuration: |
| 23 | + |
| 24 | +| Field | Value | |
| 25 | +|---|---| |
| 26 | +| **Add or Select Image** | The `nvcr.io/nim/...` image path (entered manually, without the tag) | |
| 27 | +| **Container Tag** | The image tag (e.g. `latest`) | |
| 28 | +| **Container Port** | `8000` | |
| 29 | +| **Protocol** | `HTTP` | |
| 30 | +| **Health check path** | `/v1/health/ready` | |
| 31 | +| **Image Registry Username** | `$oauthtoken` (literal string — not a variable) | |
| 32 | +| **Image Registry Password** | Your [NGC API Key](https://ngc.nvidia.com) | |
| 33 | + |
| 34 | +Leave **Add command** empty — the image's default entrypoint starts the server. Under **Optional Details → Environment Variables**, also add: |
| 35 | + |
| 36 | +| Key | Value | |
| 37 | +|---|---| |
| 38 | +| `NGC_API_KEY` | Your NGC API Key | |
| 39 | + |
| 40 | +The NGC API Key is needed twice: the registry credentials let CCluster pull the image from `nvcr.io`, and the `NGC_API_KEY` environment variable lets the container download model weights on first boot. Without the environment variable, the container starts but fails to load the model. |
| 41 | + |
| 42 | +<Note> |
| 43 | +NIM downloads model weights at startup, so the first boot can take several minutes for large models. The deployment stays in a pending state until the `/v1/health/ready` probe passes. |
| 44 | +</Note> |
| 45 | + |
| 46 | +From here the deployment follows the standard General Inference flow — select the cluster and hardware, click **Deploy**, and monitor the deployment until it is ready. See [General Inference](/apps/inference) for details. Check the model's page on [build.nvidia.com](https://build.nvidia.com/explore/discover) for the GPU and memory each NIM supports. |
| 47 | + |
| 48 | +Once ready, query the endpoint like any OpenAI-compatible endpoint. List the served model identifier first, then send requests: |
| 49 | + |
| 50 | +```bash |
| 51 | +# Find the model identifier served by this NIM |
| 52 | +curl https://<endpoint_url>/v1/models \ |
| 53 | + -H "Authorization: Bearer <your_bearer_token>" |
| 54 | + |
| 55 | +# Chat completion |
| 56 | +curl https://<endpoint_url>/v1/chat/completions \ |
| 57 | + -H "Authorization: Bearer <your_bearer_token>" \ |
| 58 | + -H "Content-Type: application/json" \ |
| 59 | + -d '{ |
| 60 | + "model": "meta/llama-3.1-8b-instruct", |
| 61 | + "messages": [{"role": "user", "content": "Hello"}], |
| 62 | + "max_tokens": 256 |
| 63 | + }' |
| 64 | +``` |
| 65 | + |
| 66 | +<Tip> |
| 67 | +Every endpoint is protected — there are no public endpoints. Secure access with a Bearer token, an mTLS client certificate, or both. For mTLS, select **Make it a private endpoint?** and CCluster generates a TLS certificate that clients must present. See [Securing Endpoints](/resources/private) for details. |
| 68 | +</Tip> |
| 69 | + |
| 70 | +## What's next |
| 71 | + |
| 72 | +<CardGroup cols={3}> |
| 73 | + <Card |
| 74 | + title="General Inference" |
| 75 | + icon="circle-nodes" |
| 76 | + href="/apps/inference" |
| 77 | + > |
| 78 | + Deploy and scale any containerized model on CCluster. |
| 79 | + </Card> |
| 80 | + <Card |
| 81 | + title="Securing Endpoints" |
| 82 | + icon="lock" |
| 83 | + href="/resources/private" |
| 84 | + > |
| 85 | + Protect your endpoints with Bearer tokens and mTLS certificates. |
| 86 | + </Card> |
| 87 | + <Card |
| 88 | + title="Managing Vault Objects" |
| 89 | + icon="key-skeleton-left-right" |
| 90 | + href="/resources/vault" |
| 91 | + > |
| 92 | + Store the registry credentials and API keys your deployments use. |
| 93 | + </Card> |
| 94 | +</CardGroup> |
0 commit comments