Fix ENOBUFS in ensureService during Docker image pulls

[Copilot]

execSync with stdio: 'pipe' in ensureService buffers all child-process output through Node's 1 MiB maxBuffer. On first-run pulls of large Docker images, this causes ENOBUFS, killing the process and failing env bootstrap even when Docker is healthy.

Changes

• src/env/service-manager.ts
  • Import spawn alongside execSync
  • Replace the execSync call in ensureService with await this.runComposeUp(cmd, env)
  • Add private runComposeUp helper using spawn with stdio: ['ignore', 'inherit', 'pipe']:
    • stdout → inherit (streamed to terminal, no buffer limit)
    • stderr → collected into Buffer[] and attached to the rejection as { status, stdout, stderr } — preserving the shape wrapComposeStartError uses for pull-auth / daemon / missing-CLI classification
    • error event → same shape with status: null for spawn-level failures (e.g. docker not on PATH)

private runComposeUp(cmd: string, env: NodeJS.ProcessEnv): Promise<void> {
  return new Promise<void>((resolve, reject) => {
    const proc = spawn(cmd, { shell: true, stdio: ['ignore', 'inherit', 'pipe'], env });
    const stderrChunks: Buffer[] = [];

    proc.stderr?.on('data', (chunk: Buffer) => stderrChunks.push(chunk));

    proc.on('close', (code) => {
      if (code === 0) { resolve(); return; }
      const stderr = Buffer.concat(stderrChunks).toString('utf8');
      reject(Object.assign(new Error(`docker compose exited with code ${code}`), { status: code, stdout: '', stderr }));
    });

    proc.on('error', (spawnErr) => {
      reject(Object.assign(spawnErr, { status: null, stdout: '', stderr: spawnErr.message }));
    });
  });
}

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

Continue Tasks: ✅ 1 no changes — View all