Goal: Run NVIDIA Triton Inference Server locally using only free, open tools, serve the official example model repository, verify it's healthy, and then add a new model of your own to the repository — giving you a repeatable template for standing up any Triton deployment at no cost. Steps:
git clone https://github.com/triton-inference-server/tutorials.git. This gives you the "Conceptual Guide Part 1" materials referenced below.docker pull nvcr.io/nvidia/tritonserver:<xx.yy>-py3 (use the latest tag available to you, matching your CPU/GPU setup — a CPU-only machine can drop the --gpus=1 flag in the next step and Triton will still run, just without GPU-accelerated backends).docker run --gpus=1 --rm -p8000:8000 -p8001:8001 -p8002:8002 -v /full/path/to/docs/examples/model_repository:/models nvcr.io/nvidia/tritonserver:<xx.yy>-py3 tritonserver --model-repository=/models.curl localhost:8000/v2/health/ready. You should get an HTTP 200 back. If you don't, check the container logs first — most early failures are path or permissions issues with the volume mount, not a broken model.tutorials repo you cloned) end to end: convert a model, hand-write its config.pbtxt, and query it via both the HTTP and gRPC endpoints.1/) containing the model file, and a config.pbtxt declaring the model name, backend, max batch size, and input/output tensors.config.pbtxt input/output shapes actually match what the model expects — the two most common beginner mistakes covered in this week's lecture.Deliverables: Submit (a) a short write-up (1-2 pages) describing your steps, the curl health-check output, and any errors you hit and how you fixed them, and (b) your final config.pbtxt plus a screenshot or terminal capture of a successful query response from your self-added model.