skills.rest
NVIDIA-Omniverse
NVIDIA-OmniverseOFFICIAL
Explore all skills by this author →
Website𝕏@nvidiaomniverseGitHub

deploy-ovrtx-docker

Deploy the OVRTX rendering API as a Docker Compose service.

179|21|Updated Apr 28, 2026
Search Tags:#deployment#rendering#docker#gpu#endpoint#docker-compose#ovrtx
One-click install
npx skills add https://github.com/NVIDIA-Omniverse/content-agents --skill deploy-ovrtx-docker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploy-ovrtx-docker
Source: https://github.com/NVIDIA-Omniverse/content-agents/tree/main/.agents/skills/deploy-ovrtx-docker
Command: npx skills add https://github.com/NVIDIA-Omniverse/content-agents --skill deploy-ovrtx-docker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploys the OVRTX rendering API standalone via Docker Compose so one or more agent CLIs / services can point at it as a shared rendering endpoint. Use when user wants to run OVRTX standalone, deploy a shared rendering service, separate the rendering endpoint from an agent service, expose OVRTX to multiple callers, or set RENDER_ENDPOINT to a dedicated render host.

Core Features & Use Cases

  • Standalone rendering API: decouples the rendering endpoint from individual agent stacks to enable shared infrastructure.
  • Multi-client support: allow multiple CLIs/services to point at a single OVRTX endpoint for consistent rendering.
  • Simplified deployment and lifecycle: manage the rendering endpoint with Docker Compose and standard Docker tooling.

Quick Start

Launch the standalone OVRTX rendering API using the provided docker-compose file and verify readiness via the /health endpoint.

Frequently Asked Questions about deploy-ovrtx-docker

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

FAQPage Schema
How do I deploy a shared rendering endpoint for multiple agent CLIs?▼

Deploy a standalone OVRTX rendering API via Docker Compose to create a shared rendering endpoint, allowing multiple agent CLIs to connect to a single dedicated render host.

What is the best way to decouple a rendering service from an agent stack?▼

Run the OVRTX rendering API independently via Docker Compose to separate the rendering endpoint from the agent service and enable shared rendering infrastructure.

Do I need a GPU and NVIDIA toolkits to run a Docker-based rendering API?▼

Yes, running this Docker-based rendering API requires Docker, Docker Compose, NVIDIA toolkits, and a GPU with sufficient VRAM to handle the rendering workload.

How do I verify that my standalone Docker rendering endpoint is ready?▼

Verify the readiness of your standalone Docker rendering endpoint by checking the /health endpoint and confirming the gpu_initialized flag is set to true.

Can I expose a single OVRTX rendering host to multiple callers?▼

Yes, you can expose a single OVRTX rendering host to multiple callers by deploying it as a standalone Docker service, allowing various CLIs and services to point at the shared endpoint.

Related Skills

Explore More Software Engineering Skills→
NVIDIA-OmniverseNVIDIA-Omniverse
179

deploy-physics-agent-docker

Deploy physics-agent-service locally with Docker Compose and OVRTX GPU sidecar.

Official
Intermediate
dseirz-rgbdseirz-rgb

deployment-verification

Verify post-release deployments on Vercel or GCP with health and readiness checks.

Community
Advanced
nesihaver-ILnesihaver-IL

aws-agentcore

Build production-grade AI agents on AWS with AgentCore components.

Community
Intermediate
NVIDIA-OmniverseNVIDIA-Omniverse
179

deploy-material-agent-docker

Deploy material-agent-service and OVRTX rendering API locally with Docker Compose.

Official
Advanced