Skip to content

Document microVM consolidation on Cloud Hypervisor #58784

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 1 commit into from
Sep 5, 2026
+45 −3
Merged

Document microVM consolidation on Cloud Hypervisor #58784

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 42 additions & 0 deletions docs/src/content/docs/blog/2026-09-05-cloud-hypervisor-consolidation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
---
title: "MicroVM Support Is Consolidating on Cloud Hypervisor"
description: "gh-aw is consolidating its specialized sandbox runtimes on the Cloud Hypervisor microVM implementation."
authors:
- copilot
date: 2026-09-05
metadata:
seoDescription: "Learn why gh-aw deprecated the gVisor and Docker sbx runtimes and is consolidating microVM support on Cloud Hypervisor."
---

GitHub Agentic Workflows is consolidating its specialized sandbox runtime support on `cloud-hypervisor`. The `gvisor` and `docker-sbx` runtime options are deprecated and will be removed in a future release.

`docker-sbx` introduced a KVM-backed microVM boundary, while `gvisor` provided a user-space kernel between the agent container and host kernel. Maintaining both paths alongside Cloud Hypervisor created separate installation, compatibility, and troubleshooting surfaces. Consolidating on one microVM implementation makes the stronger isolation path more consistent and easier to evolve.

## What changes

The default `docker` runtime remains available and continues to run AWF with network isolation and proxy enforcement. For workflows that require a hardware-virtualized boundary, `cloud-hypervisor` is now the supported direction:

```aw wrap
---
on: issues
sandbox:
agent:
runtime: cloud-hypervisor
---

Investigate this issue.
```

Cloud Hypervisor support is currently in preview and requires a GitHub-hosted Ubuntu x86_64 runner with `/dev/kvm`. The compiler adds the required host checks and provisions digest-pinned runtime assets.

## Migrating existing workflows

Review workflows that explicitly set `runtime: gvisor` or `runtime: docker-sbx`. Select `cloud-hypervisor` when the workflow runs on an eligible GitHub-hosted runner and needs a microVM boundary. Otherwise, remove the runtime setting to use the default Docker profile.

Compile each updated workflow and review the generated lock file:

```bash
gh aw compile
```

The deprecated values remain documented during the transition, but new workflows should use either the default Docker runtime or `cloud-hypervisor`. See [Agent Runtime Selection](/gh-aw/reference/agent-runtimes/) for requirements and tradeoffs.
6 changes: 3 additions & 3 deletions docs/src/content/docs/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ import WorkflowHero from '../../components/WorkflowHero.astro';

Wake up to ready-to-review repository improvements — automated triage, CI insights, docs updates, and test enhancements. Use event-triggered and scheduled jobs to augment your existing, deterministic CI/CD with AI-powered intelligence.

GitHub Agentic Workflows deliver repository automation: simple markdown workflows running the coding agents you know and love, in GitHub Actions, with strong guardrails and security-first design principles. Supported AI engines include GitHub Copilot, Claude Code, Google Gemini and OpenAI Codex. Supported sandbox runtimes include standard Docker, `gvisor`, `docker-sbx`, and preview `cloud-hypervisor`.
GitHub Agentic Workflows deliver repository automation: simple markdown workflows running the coding agents you know and love, in GitHub Actions, with strong guardrails and security-first design principles. Supported AI engines include GitHub Copilot, Claude Code, Google Gemini and OpenAI Codex. Supported sandbox runtimes include standard Docker and preview `cloud-hypervisor`.

Developed by GitHub, GitHub Agentic Workflows run with strong guardrails, using safe outputs and sandboxed execution to help keep your repository safe.

Expand Down Expand Up @@ -69,8 +69,8 @@ AI agents can be manipulated by prompt injection or malicious content. GitHub Ag
<FeatureCard icon="key" title="Credential Isolation" href="/gh-aw/introduction/architecture/#agent-workflow-firewall-awf">
The API proxy isolates the agent from credentials
</FeatureCard>
<FeatureCard icon="container" title="MicroVM Isolation" href="/gh-aw/reference/glossary/#docker-sbx">
Run agents in KVM-isolated Docker sbx microVMs on compatible runners
<FeatureCard icon="container" title="MicroVM Isolation" href="/gh-aw/reference/glossary/#cloud-hypervisor">
Run agents in Cloud Hypervisor microVMs on compatible runners
</FeatureCard>
<FeatureCard icon="filter" title="Integrity Filtering" href="/gh-aw/reference/integrity/">
Reduce prompt-injection risk by filtering untrusted GitHub content
Expand Down
Loading