deploy-texture-agent-docker

name	deploy-texture-agent-docker
description	Deploy the texture-agent-service locally using Docker Compose, including hosted/simple image generation, optional local FLUX.2 and LLM NIM sidecars, and an operator-mounted Texture Variation API / Step1X-compatible overlay with OVRTX. Use when user wants to run texture agent with docker, docker compose, set up local deployment, run UV-aware texture projection locally, validate an existing Step1X-compatible backend, start the texture-agent service containers, or route image generation to local sidecars. Trigger phrases include "docker compose texture", "docker deploy texture", "run texture agent locally", "start texture agent docker", "texture agent up", "local texture deployment", "image-gen sidecar", "step1x overlay", "uv-aware texture".
version	0.2.1
author	NVIDIA Content Agents
tags	["content-agents","texture-agent","docker","image-generation","step1x","texture-variation-api","ovrtx","deployment"]
tools	["Shell","Docker","curl","Python","Filesystem"]
compatibility	Requires Docker daemon, Docker Compose v2.24+, compose-interpolated TA/TEXTURE/OVRTX settings in the shell or repo-root .env passed with --env-file, provider keys for hosted backends, free host port 8001 for the main service, optional ports 8005 and 8006 for local NIM sidecars, and optional ports 8019, 8018, and 8002 plus NVIDIA GPU support for the operator-mounted Step1X-compatible overlay. Step1X overlay runs require NVIDIA Container Toolkit and a reviewed runtime mounted with TEXTURE_STEP1X_HOST_RUNTIME.

Deploy Texture Agent Service with Docker Compose

Deploy the Texture Agent service locally with Docker Compose. Pick the smallest mode that matches the user's goal:

1. Default service: texture-agent-service on port 8001, using the configured hosted/simple image-generation backend.
2. Local NIM sidecars: optional FLUX.2 image generation and LLM sidecars for local image-gen or auto-prompt calls.
3. Operator-mounted Step1X-compatible overlay: Texture Agent plus the simple Texture Variation API sidecar, a Step1X-compatible API adapter, and OVRTX rendering. The public release does not install or download the Step1X runtime.

When to Use

• Use when the user wants to run texture-agent-service locally with Docker Compose, with hosted image-gen or optional local FLUX.2 / LLM NIM sidecars.
• Use when the user wants UV-aware texture generation through a Texture Variation API backend, including a Step1X-compatible runtime they already mounted.
• Use when the user wants a fake-runner smoke test for container wiring without Step1X model weights.
• Use quickstart for a shorter first local POC, and use deploy-collection when running multiple Content Agents together.

Limitations

• The main service owns host port 8001, overlapping other local Content Agent stacks that expose a primary service.
• The default hosted nim image backend is text-only and cannot accept reference images for tightly matched PBR sets; use a conditioning-capable backend or an operator-mounted Texture Variation API backend for UV-aware texture evidence.
• Local NIM sidecars require idle GPUs, NGC auth, and model warm-up time.
• The Step1X runtime, model weights, third-party checkouts, and caches are not committed to this repository. The public Compose overlay requires a runtime directory that has already been prepared and reviewed by the operator.
• Full Step1X-compatible validation needs GPU memory and runtime assets. Two GPUs are preferred: one for the texture backend, one for OVRTX.
• The Step1X-compatible overlay validates service topology and compatible USD assets; it is not a blanket guarantee that every arbitrary USD can be edited without target-specific material scope, UV, or backend configuration.
• The overlay defaults to the Step1X-compatible backend for normal requests but also starts the simple Texture Variation sidecar. Requests can select texture_backend=simple_image_gen without restarting or redeploying the stack.
• OVRTX mounts the session volume read-only and host at so render requests can resolve generated USDs and host temp paths.