Files
James Stringer 5a3494501c Scrub remaining cloud-image/cidata references from comments (comments only)
The cloud-image install flow is gone; reword the last comments that still
referenced it:
  - asb_core.c: "Linux cloud-image creates" -> "Linux ISO creates"
  - disk_util.c: drop the "Ubuntu cloud-image parent ~2.5 GB" rationale
    from vhdx_create_differencing_resized (now describes the generic
    inherit-then-resize behavior)
  - disk_util.h: stage_linux_agent_and_extras doc no longer says "same
    content the cidata builder used to ship"
  - appsandbox-agent.c: "autoinstall lets the user pick" -> "the create-VM
    modal lets the user pick"
2026-05-30 14:49:35 -04:00
..
2026-05-19 20:21:43 -04:00
2026-05-19 20:21:43 -04:00
2026-05-19 20:21:43 -04:00

App Sandbox Linux guest daemons

In-VM Linux daemons that speak the same vsock wire protocol the Windows App Sandbox host expects. See docs/linux-idd-implementation-plan.md in the repo root for full architecture and wire-protocol reference.

Daemons (this directory)

Binary Channel Listens on Privilege Status
appsandbox-agent control vsock :1 root (system) implemented
appsandbox-input input vsock :3 root (system) planned
appsandbox-display frames + cursor vsock :2 root (system) planned
appsandbox-clipboard clipboard vsock :5, :6 user (user unit) planned

Build (inside the VM)

sudo apt-get install -y build-essential
make

Install + enable (inside the VM)

sudo make enable

This installs to /usr/local/bin/, drops the systemd unit into /etc/systemd/system/, runs daemon-reload, then systemctl enable --now appsandbox-agent.service.

Smoke test

systemctl status appsandbox-agent
journalctl -u appsandbox-agent -f

You should see listening on AF_VSOCK port 1. Once the host-side Phase 1 service-GUID switch lands, the App Sandbox UI's agent dot will turn green within a few seconds of the unit being active.

Uninstall

sudo make disable
sudo rm /usr/local/bin/appsandbox-agent /etc/systemd/system/appsandbox-agent.service
sudo systemctl daemon-reload