Runpod adds in-Pod container builds and template guidance for agents

Runpod’s November 2026 update adds Weld, a way to build container images inside a Runpod Pod without a Docker daemon, alongside guidance for creating and managing Pod templates.
- Runpod Weld builds container images inside a Runpod Pod.
- Weld works without a Docker daemon.
- Runpod provides guidance on public and private template settings.
- The example uses PyTorch and a short GPU-check script.
- A custom image can be pushed to Docker Hub and saved as a private Pod template.
Build container images directly on a Pod
Runpod Weld is designed for a workflow in which code is already stored on a Pod. It lets users build container images inside that Pod, without requiring a Docker daemon.
The feature is presented as a way to build the image where the code is located. The source does not provide additional details about supported image formats, pricing, availability or performance.
A guide to public and private templates
The update also includes a primer on how Runpod templates function. Its focus is the distinction between public and private template settings, giving users guidance on how those options affect the templates they create or use.
Templates are central to the setup described in the update. They allow a Pod to start with a defined environment instead of requiring the same configuration to be recreated each time.
From a custom image to a reusable Pod setup
Runpod’s example walks through building a first custom template. The process starts with creating a custom Docker image that includes PyTorch and a short GPU-check script.
The image is then pushed to Docker Hub and saved as a private Runpod Pod template. According to Runpod, this means every new Pod can start with the user’s setup already in place.
Together, the materials connect image creation with repeatable Pod configuration. Weld addresses where a container image can be built, while the template guide explains how that image can be retained as a private starting point for new Pods.
What the update means for Runpod users
The announcement gives users a path from code on a Pod to a reusable environment: build an image, include the required tools and checks, push it to Docker Hub, and save it as a private template. The example specifically uses PyTorch and a GPU-check script, making the workflow relevant to the setup described for GPU workloads.
Runpod’s source frames the update around agents, but it does not provide claims about agent performance or broader market effects. Its stated focus is the practical setup of container images and Pod templates.
RunPod: What’s new in Runpod for Agents: November 2026


