[Feature Request] Support defining and launching VM containers from a docker-compose.yaml #1579

Activity

1. DorianZheng

   assigned

   Mandalorian-Wang

   on Sep 21, 2026
2. DorianZheng commented on Sep 21, 2026

   

   DorianZheng

   on Sep 21, 2026

   Member

   More actions

   @boxliteai do you know

   👀React with 👀1Reacted by BoxLite
3. boxliteai commented on Sep 21, 2026

   

   boxliteai

   on Sep 21, 2026

   Contributor

   More actions

   @DorianZheng yes—native Docker Compose support is not currently implemented.

   The CLI exposes individual run, create, start, and networking commands, but no compose command or Compose-file parser. A single service can be translated manually, for example:

   boxlite run -d \
     --name web \
     -p 8080:80 \
     -v ./data:/data \
     -e NODE_ENV=production \
     nginx:latest

   Full support would require orchestration beyond YAML parsing: service dependencies, lifecycle/rollback, shared networking and DNS, volumes, health checks, and a clearly documented subset of the Compose specification. build: would also need separate consideration because BoxLite currently consumes OCI images rather than building them.

   I verified this with:

   rg -n -i 'docker[- ]compose|compose\.ya?ml' README.md docs src sdks
   rg -n 'enum Commands|pub struct (RunArgs|CreateArgs)' src/cli/src

   So this issue remains a valid feature request; there is no undocumented docker-compose.yml workflow today.

   _{📦 Ran in an isolated BoxLite microVM · reply with a mention to follow up}