Cua Fleets Adds Bring-Your-Own VM Images for Agent Sandboxes
- Source
- x.com
- Date
1/ You can now bring your own Linux or Windows VM images to Cua Fleets. Publish them to a registry, just like Docker images, and run your agents on desktops with your tools already installed. Get started: https://t.co/Iso7LYXACd
2/ Prepare your desktop before Fleet boots it. Choose the OS, install your tools, and configure startup services. Package the bootable guest disk as an OCI/containerDisk artifact.
3/ Pin the image by digest. A mutable tag can point to a different image later. An immutable digest identifies the exact boot image your pool uses. Publish a new image when you want to change the setup.
4/ Reference your image with Image.from_registry(), then launch it with Sandbox.ephemeral(). The attached Python example uses Linux. The guide's default setup expects your image to start computer-server on port 8000.
Context
In a thread announcing the feature, Cua describes preparing a desktop before Fleet ever boots it: choose an OS, install the tools an will need, configure any startup services, then package the resulting bootable disk as an OCI or containerDisk artifact and publish it to a registry.
Cua recommends pinning that image by its digest rather than a mutable tag, since a tag can later point to a different image while a digest identifies the exact boot image a pool is using; changing the setup means publishing a new image rather than mutating one already in use. In Cua's Python SDK, a published image is referenced with Image.from_registry() and launched with .ephemeral(), and the guide's default configuration expects the image to start Cua's computer-server on port 8000 so Cua Driver can control it.
Checking sign-in…
Loading comments…