Vyomi v2.0.9.2

Docker Compose is back — as an assisting tool, not a host installer. Every install method now boots the appliance inside Multipass (the boundary).

Added

• docker compose up as a front door to the Multipass appliance (Compose provider). docker-compose stays a first-class launch pad for developers, but as an assisting tool, not a host installer: the vyomi launcher now implements the Docker Compose provider protocol (vyomi compose --project-name P up|down|stop → emits {"type":"info|error",...} JSON, routes to vyomi up/down/stop). With the thin packaging/compose-provider/docker-compose.yml (a provider service, type: vyomi), docker compose up boots the appliance inside Multipass — same boundary, EC2/LXD compute works. Zero extra packaging: Compose resolves type: vyomi to the vyomi binary every native package already puts on PATH (no separate CLI plugin). Validated on Compose v5.1.3.

Changed

• Multipass is the appliance boundary for every install method. brew / deb / rpm / scoop / Docker Compose all now provision the appliance inside a Multipass VM via vyomi up. The standalone "run the stack on host Docker" path is retired from the portal install steps — running outside the boundary breaks HTTPS, instance workspaces, and EC2/VM compute, and produces host-specific inconsistencies the appliance can't control. No runtime change: the launcher already boots the same docker-compose stack inside the VM; this is a packaging/install-story decision (portal install_catalog routes the Docker Compose method to vyomi up). The repo's docker-compose.yml remains for advanced/CI use but is no longer a user-facing appliance install.

---

Artifacts

• SHA256SUMS
• cloud-learn-0.1.0.tar.gz
• cloud-learn-2.0.9.2-1.noarch.rpm
• cloud-learn-2.0.9.2.tar.gz
• cloud-learn_2.0.9.2_all.deb

Docker image: docker pull vyomi/appliance:2.0.9.2
Install: curl -fsSL https://raw.githubusercontent.com/vyomi-cloud/appliance/main/install.sh | bash
SHA256 checksums: see SHA256SUMS in attached artifacts.