deploy-texture-agent-docker

Deploy texture-agent-service locally with Docker Compose and optional FLUX.2 NIM sidecar.

179|21|Updated Apr 28, 2026

Search Tags:#docker #deploy #docker-compose #local-development #image-gen #texture-agent

Ready to run

npx skills add https://github.com/NVIDIA-Omniverse/content-agents --skill deploy-texture-agent-docker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploy-texture-agent-docker
Source: https://github.com/NVIDIA-Omniverse/content-agents/tree/main/.agents/skills/deploy-texture-agent-docker
Command: npx skills add https://github.com/NVIDIA-Omniverse/content-agents --skill deploy-texture-agent-docker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploys the texture-agent-service locally using Docker Compose, with an optional FLUX.2 NIM image-gen sidecar to enable local deployment and offline image generation.

Core Features & Use Cases

Deploys texture-agent-service via Docker Compose for local testing and development.
Optional FLUX.2 NIM sidecar for local image generation routing.
Supports environment configuration, health checks, and logs for repeatable local workflows.
Use case: developers validating texture generation pipelines locally before cloud deployment.

Quick Start

Start the stack with docker compose up from the repository root and verify the service is reachable on port 8001.

Frequently Asked Questions about deploy-texture-agent-docker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I deploy a texture agent service locally using Docker Compose?▼

To deploy the texture agent locally, run the texture-agent-service via Docker Compose from the repository root. This validates environment configuration and container readiness to enable repeatable local testing workflows.

Can I run local image generation offline with the texture agent?▼

Yes, you can enable local image generation by deploying an optional FLUX.2 NIM sidecar. This sidecar routes image generation tasks offline while running the texture-agent-service through Docker Compose.

Do I need Docker Compose to test the texture generation pipeline locally?▼

Yes, Docker Compose is required to deploy the texture-agent-service locally. It manages container orchestration, validates environment configuration, and ensures the service is reachable on port 8001.

What port does the texture agent service use for local development?▼

The texture agent service uses port 8001 for local development. After running docker compose up, you verify the service is reachable on this port to confirm successful local deployment.

How does the FLUX.2 NIM sidecar work with Docker Compose for texture generation?▼

The FLUX.2 NIM sidecar integrates with the texture-agent-service via Docker Compose to route image generation locally. It validates sidecar health to ensure repeatable offline local experimentation.

Why validate environment configuration before starting the texture agent containers?▼

Validating environment configuration before starting the texture agent ensures container readiness and proper service routing. It prevents deployment failures and enables repeatable local testing workflows with Docker Compose.