Run Docker Compose integration tests

Run Docker Compose inside a microVM when a test needs several containers. The inner daemon uses the sandbox’s flat root disk and never receives the host’s /var/run/docker.sock. This example assumes ./my-project contains compose.yaml and a test service named test.

Run the integration tests

Start Docker

msb run -d --name compose-ci --replace \
  --memory 2G --root-disk flat:10G --max-duration 10m \
  docker:27.5.1-dind

msb run -d --name compose-ci --replace `
  --memory 2G --root-disk flat:10G --max-duration 10m `
  docker:27.5.1-dind

The flat root gives Docker a direct ext4 filesystem for its own overlay storage, avoiding an overlay-on-overlay stack. Its 10 GiB capacity covers the image, project, build cache, and containers.Copy the project into the running sandbox. This happens after creation because flat roots do not currently accept create-time rootfs patches such as --copy-dir:

msb cp ./my-project/. compose-ci:/workspace

The official dind image starts dockerd. Wait for it before sending Compose commands:

for attempt in $(seq 1 60); do
  msb exec compose-ci -- docker info >/dev/null 2>&1 && break
  sleep 1
done
msb exec compose-ci -- docker info >/dev/null

for ($attempt = 1; $attempt -le 60; $attempt++) {
  msb exec compose-ci -- docker info *> $null
  if ($LASTEXITCODE -eq 0) { break }
  Start-Sleep -Seconds 1
}
msb exec compose-ci -- docker info *> $null
if ($LASTEXITCODE -ne 0) { throw 'Docker did not become ready' }

Run the tests

msb exec --timeout 5m --workdir /workspace compose-ci -- \
  docker compose up --build \
    --abort-on-container-exit \
    --exit-code-from test

msb exec --timeout 5m --workdir /workspace compose-ci -- `
  docker compose up --build `
    --abort-on-container-exit `
    --exit-code-from test

Replace test with the service whose exit code should decide the CI result. msb exec returns that code to the host.

msb cp makes a guest copy. Use a clean project directory, and do not copy credentials or unrelated files into the sandbox.

Clean up

Stop the Compose stack inside the sandbox:

msb exec --workdir /workspace compose-ci -- docker compose down --volumes

Remove the sandbox:

msb rm -f compose-ci

Removing the sandbox also removes Docker’s image and build cache. Keep the sandbox between trusted runs if you want to reuse that cache; do not carry a writable cache across repositories or trust boundaries.

Never mount the host Docker socket into the sandbox. Control of that socket is normally control of the host Docker daemon and defeats the microVM boundary.

⌘I

Agents

CI/CD

Docker

Sandbox Workflows

Automation & Tooling

Data & Observability

Run Docker Compose integration tests

Run the integration tests

​Run the integration tests

Run the integration tests