← ClaudeAtlas

cloud-runlisted

Deploy headless robotics / sim / demo containers to Google Cloud Run: the build → Artifact Registry → Cloud Run path plus the gotchas that bite sim workloads (no UDP multicast for gz-transport/DDS, CPU allocated only while a request is open, session affinity for per-visitor instances, request timeout / concurrency for long-lived WebSockets, VPC subnet sizing). Use when: 'deploy to Cloud Run', 'gcloud run deploy', 'Cloud Build', 'Artifact Registry', 'host the sim in the cloud', 'Cloud Run WebSocket / Foxglove bridge times out', 'session affinity', '--no-cpu-throttling', 'GZ_RELAY / GZ_IP on Cloud Run', deploy auth from CI with a GCP service-account key. Owns the Cloud Run deploy mechanics that live-demo and environments point at. Not for: the demo orchestrator, session gateway, or mission-control page (live-demo); GPU-cloud/RunPod or uv-vs-Docker choice (environments); general non-robotics gcloud/GCP basics (upstream Google docs).
robium-ai/robium · ★ 6 · DevOps & Infrastructure · score 74
Install: claude install-skill robium-ai/robium
# cloud-run The deploy target for robium's headless robotics and demo containers: a sim + bridge (or a policy server) built into an image, pushed to Artifact Registry, and run on Google Cloud Run so a browser can reach it — optionally one private instance per visitor, scale-to-zero when idle. This skill consolidates the Cloud-Run-specific mechanics and the robotics/headless gotchas that were hard-won deploying a Gazebo Harmonic + Nav2 stack (robium's nav-trial demo, 2026-07-12/13). It stays thin on general gcloud/GCP usage — that lives in Google's own docs — and embeds only what a robotics container hits that a plain web service never does. ## When to use this skill - Building and deploying any headless robotics/sim/demo container to Cloud Run: the `gcloud` / Cloud Build → Artifact Registry → `gcloud run deploy` path, and the flag set a sim workload needs (CPU/memory, timeout, concurrency, affinity). - Debugging a robotics container that runs locally but misbehaves on Cloud Run: gz/DDS discovery silent (no multicast), sim boot freezes (CPU throttled between requests), WebSocket drops, affinity cookie ignored, deploy fails on VPC IPs. - Wiring deploy auth from CI/servers with a GCP service-account key. - The trigger phrases in the description: 'deploy to Cloud Run', 'gcloud run deploy', 'Cloud Build', 'Artifact Registry', 'session affinity', '--no-cpu-throttling', 'GZ_RELAY on Cloud Run', 'Cloud Run WebSocket timeout'. - Cross-references — go to the sibling skil