Docker's workflow for Hyper-V

Now your AI can launch and control throwaway Windows 11 machines with Docker's commands and file formats.

Needs a Windows PC with Hyper-V enabled, build 26100 or later. Free for personal use and small businesses.

Paste this into your agent
You are going to test Windows software on Windows virtual machines, using East India.

East India is a service on my Windows PC that runs Hyper-V virtual machines the way Docker runs containers. Images are Windows disks built from recipes called Endiafiles, which use Dockerfile syntax with some differences. Machines come from Compose files. The endia command line follows Docker's commands and options wherever Docker has one.

1. Read both guides before you start:
   https://raw.githubusercontent.com/teaToolkit/EastIndia/main/docs/using-eastindia.md
   https://raw.githubusercontent.com/teaToolkit/EastIndia/main/docs/testing-windows-apps.md

2. Connect to the service. …

What to ask your agent

Once your AI is connected, ask to control Windows in plain words.

'Install our Windows service on clean Windows and check that it starts and answers.'

Your AI reports whether the service started on a clean Windows machine and answered over the network, with its event-log entries as evidence.

Testing a Windows service ›

'Open the Orders app, enter an order, save it, and show me screenshots before and after.'

Your AI reads the program's window, enters the order through it and takes screenshots before and after. When the image's recipe allows it, it answers elevation prompts too.

Driving the screen ›

'Run the server with three clients on a private network and check every order arrives.'

Your AI launches a server and three clients on a private network, runs the clients at once and collects every machine's results and the server's logs. Then it removes everything.

Walkthrough: a fleet tested together ›

'Keep a machine up while we work on the UI, and re-test after every change.'

One machine stays up all day. After each change, your AI copies in the new build, runs it and takes screenshots, without restarting Windows.

Walkthrough: one machine while you work ›

Not just for testing

Anything you would do with a throwaway Windows machine, you can do with East India, through your AI or by hand.

Trying unknown software

Run an unfamiliar installer or program on a machine that is deleted afterwards.

A desktop for your AI

Your AI can control any Windows-only program, even from Linux or a sandbox.

Demos and training labs

Launch identical Windows machines for a session from one Compose file, and remove them afterwards.

Customer set-ups

Build a machine with a customer's Windows settings to reproduce their bug.

Getting started

Prepare your PC once, then give your AI one prompt. It tells you when it needs you.

  1. Prepare your PC

    Run the MSI from GitHub on your Hyper-V PC, then save Microsoft's Windows 11 installation disc in your image folder.

  2. Paste the prompt

    Give your AI the Get started prompt, in the repository of the software you want tested.

  3. Your agent tests

    From a Docker sandbox, it first asks you to run two commands on the PC. If there is no Windows image yet, it asks which installation disc to use and prepares one. Then it runs the test and reports the results with screenshots and logs.

Prefer to drive it yourself?

Everything your agent does, you can do from a terminal. If you know Docker, you already know most of the endia command line.

Using East India by hand ›

Docker East India
docker build endia build
docker compose up / down endia compose up / down
docker exec, docker cp endia exec, endia cp
(none) endia desktop

Install East India, then hand over to your agent

The installer and the Linux command line for sandboxes are on GitHub.