fix(cli): probe sandbox runtime before selecting it (#7734)

* fix(cli): probe sandbox runtime before selecting it

Sandbox selection treated PATH presence as proof a runtime works, so an
installed-but-unusable docker (daemon stopped, socket unreachable, user not in
the docker group) was still selected and the podman branch below it became
unreachable. Each candidate is now probed with `version` — the cheapest command
that still contacts the daemon — and the first one that actually runs wins.

When nothing usable is found, the error names the runtime that broke and quotes
its failure instead of claiming nothing is installed. An explicit QWEN_SANDBOX
choice is never silently redirected; it fails with the daemon error attached.
sandbox-exec is not probed, being a kernel facility rather than a daemon client.

Fixes #7732

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(cli): attribute the sandbox command to its real source

The probe failure hardcoded "(from QWEN_SANDBOX)", but an explicitly named
command also arrives from --sandbox or tools.sandbox in settings. Naming the
env var unconditionally sends a user who never set it looking in the wrong
place — the same misdirection this change set out to remove.

The parenthetical is now emitted only when the env var actually supplied the
value, which also corrects the pre-existing "Missing sandbox command" message.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(cli): apply source-accurate attribution to the auto-detect errors too

The explicit-string path stopped hardcoding QWEN_SANDBOX, but the auto-detect
errors still did, so `qwen --sandbox` with a broken runtime pointed at an env
var the user never set. Both auto-detect messages now name the env var only
when it was what enabled sandboxing, and otherwise suggest --sandbox.

Also lowers the probe timeout from 10s to 5s. Probes run sequentially, so the
ceiling is paid once per wedged runtime; a healthy `docker version` answers in
roughly 200-500ms, so 5s keeps an order of magnitude of headroom while halving
the worst-case startup delay.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* test(cli): assert the sandbox probe argv and timeout

The spawnSync stub routed on command name alone, so the probe arguments
were never observed. Rewriting the probe to `docker --version` — which
prints the client build without contacting the daemon, restoring the
original defect — left all 12 tests green, as did deleting the timeout
that bounds a wedged daemon.

Validate both in the stub, so every probing test carries the check, and
pin the argv at the fallback call site where the behavior is asserted.

Reported by @wenshao in the mutation matrix on #7734 (M9, M8).

* test(cli): cover the empty-output and timeout probe branches

Two probe branches in probeSandboxCommand were unpinned, so a mutant in
either survived the whole suite:

- a non-zero exit with empty output relied on the synthesized-message
  fallback; dropping it made the probe return undefined and a broken
  runtime read as usable
- the result.error branch that the probe timeout produces had no test;
  deleting it degraded the error text with the suite still green

Each new test fails against its mutant and passes on the real code.

Reported by @qwen-code /review on #7734.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* test(cli): isolate the sandbox probe in config precedence tests

The image-precedence tests enable the sandbox and assert only which image
wins. Since the runtime probe added here spawns a real `docker version`
subprocess, and this file mocks command-exists but not child_process, the
probe runs for real. On macOS the sandbox-exec branch returns before probing,
so it passed there and on CI runners that have docker; on any other host
without a running daemon getSandboxCommand throws and all four tests fail on
image assertions they never reach.

Mock the docker/podman `version` probe to report healthy, so selection is
deterministic and the tests exercise image precedence on every platform.
Every other spawnSync call stays real.

Reported by @qwen-code /review on #7734.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(cli): cache the sandbox probe and sanitize its error output

loadSandboxConfig runs twice on a sandboxed startup, so every candidate was
probed twice — the wedged-docker-then-podman fallback paid the 5s cap twice
(~10s), which the PR description wrongly called "once per wedged runtime".
Cache each command's probe outcome per process (with a test-only reset),
mirroring the ripgrep health cache, so a runtime is contacted at most once.

The probe also returned the runtime's stderr verbatim into FatalSandboxError
messages, carrying ANSI/control bytes to the terminal. Strip them with the
existing stripAnsiAndControl helper, whose own doc names this case.

Both requested by @wenshao in the review on #7734 (items 1 and 3).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(cli): keep an all-control-character probe failure from reading as usable

The sanitizer checked the failure line for emptiness before stripping, so a
runtime whose stderr is only escape/control bytes stripped to '' — falsy — and
the broken runtime was selected as usable, reintroducing the presence-vs-
liveness bug through the sanitizer. Check emptiness after stripping and fall
back to the synthesized message.

Also drop the redundant `candidate !== 'sandbox-exec'` guard (sandbox-exec is
only a candidate once its presence is confirmed), reword the all-broken hint to
"try another installed runtime" since another may be installed but also broken,
and add tests pinning the control-character failure and the first-of-several-
broken diagnosis.

Reported by @qwen-code /review on #7734.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Harjoth Khara 2026-08-05 22:17:01 -07:00 committed by GitHub
parent 8fd0162c68
commit ec4f1e02e4
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 519 additions and 9 deletions

View file

@ -166,6 +166,40 @@ vi.mock('command-exists', () => ({
},
}));
// #7734 added a sandbox runtime probe that spawns a real `docker version`
// subprocess during sandbox selection. These tests enable the sandbox to assert
// image precedence, not which runtime is chosen, so left unmocked the probe runs
// for real and the suite fails on any non-macOS host without a running daemon
// (macOS is masked because the sandbox-exec branch returns before probing).
// Report the runtime probe healthy; leave every other spawnSync call real.
vi.mock('node:child_process', async (importOriginal) => {
const actual = await importOriginal<typeof import('node:child_process')>();
const spawnSync = vi.fn(
(command: string, args?: readonly string[], options?: unknown) => {
if (
(command === 'docker' || command === 'podman') &&
args?.[0] === 'version'
) {
return {
status: 0,
stdout: '',
stderr: '',
signal: null,
pid: 0,
output: [],
error: undefined,
};
}
return (actual.spawnSync as unknown as (...a: unknown[]) => unknown)(
command,
args,
options,
);
},
);
return { ...actual, default: { ...actual, spawnSync }, spawnSync };
});
vi.mock('@qwen-code/qwen-code-core', async (importOriginal) => {
const actualServer = await importOriginal<typeof ServerConfig>();
const SkillManagerMock = vi.fn();

View file

@ -0,0 +1,348 @@
/**
* @license
* Copyright 2025 Google LLC
* SPDX-License-Identifier: Apache-2.0
*/
import { afterEach, beforeEach, describe, expect, it, vi } from 'vitest';
import type { SpawnSyncReturns } from 'node:child_process';
const { commandExistsSync, spawnSync, platform } = vi.hoisted(() => ({
commandExistsSync: vi.fn<(cmd: string) => boolean>(),
spawnSync: vi.fn(),
platform: vi.fn<() => string>(),
}));
vi.mock('command-exists', () => ({
default: { sync: commandExistsSync },
}));
vi.mock('node:child_process', async (importOriginal) => {
const actual = await importOriginal<typeof import('node:child_process')>();
// `default` has to carry the stub too: Node builtins are CJS, so Vite's
// interop can resolve a named import through the default export.
return { ...actual, default: { ...actual, spawnSync }, spawnSync };
});
vi.mock('node:os', async (importOriginal) => {
const actual = await importOriginal<typeof import('node:os')>();
return { ...actual, platform };
});
vi.mock('../utils/package.js', () => ({
getPackageJson: vi.fn(async () => ({
config: { sandboxImageUri: 'test-image' },
})),
}));
const { loadSandboxConfig, resetSandboxProbeCacheForTest } = await import(
'./sandboxConfig.js'
);
/** A `spawnSync` result standing in for a runtime that answers `version`. */
function healthy(): Partial<SpawnSyncReturns<string>> {
return { status: 0, stdout: 'Version: 99.0.0\n', stderr: '' };
}
/**
* A runtime whose CLI is installed but cannot reach its daemon Docker
* Desktop stopped, or the user not in the `docker` group.
*/
function daemonDown(): Partial<SpawnSyncReturns<string>> {
return {
status: 1,
stdout: '',
stderr:
'Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?\n',
};
}
/**
* A runtime that exits non-zero but prints nothing a wrapper that swallows
* output, or a silent permission failure. The empty output is the point: it is
* what makes the `?? synthesized message` fallback in `probeSandboxCommand`
* load-bearing. Without that fallback the probe would return `undefined` here
* and the broken runtime would be declared usable.
*/
function brokenSilently(): Partial<SpawnSyncReturns<string>> {
return { status: 1, stdout: '', stderr: '' };
}
/**
* A wedged daemon killed at the timeout: `spawnSync` reports an `error` and a
* null status. This is the path `SANDBOX_PROBE_TIMEOUT_MS` exists for.
*/
function timedOut(): Partial<SpawnSyncReturns<string>> {
return {
error: new Error('spawnSync docker ETIMEDOUT'),
status: null,
stdout: '',
stderr: '',
};
}
/**
* Route probe results per command so a test can mix healthy and broken.
*
* The stub validates argv and the timeout, not just the command name. Both are
* load-bearing and neither is observable from the selection result: `version`
* contacts the daemon while `--version` only prints the client build, so a
* probe that drifted to `--version` would call every broken runtime healthy and
* silently restore the original bug with the selection assertions still green.
* The timeout is the only bound on a wedged daemon that accepts connections and
* never answers.
*/
function probes(byCommand: Record<string, Partial<SpawnSyncReturns<string>>>) {
spawnSync.mockImplementation(
(cmd: string, args: string[], options: { timeout?: number }) => {
const result = byCommand[cmd];
if (!result) throw new Error(`unexpected probe of '${cmd}'`);
expect(args).toEqual(['version']);
expect(options?.timeout).toBeGreaterThan(0);
return result;
},
);
}
function installed(...commands: string[]) {
commandExistsSync.mockImplementation((cmd: string) => commands.includes(cmd));
}
describe('loadSandboxConfig sandbox command selection', () => {
beforeEach(() => {
vi.clearAllMocks();
resetSandboxProbeCacheForTest();
platform.mockReturnValue('linux');
delete process.env['SANDBOX'];
delete process.env['QWEN_SANDBOX'];
});
afterEach(() => {
delete process.env['SANDBOX'];
delete process.env['QWEN_SANDBOX'];
});
it('falls back to podman when docker is installed but its daemon is unreachable', async () => {
installed('docker', 'podman');
probes({ docker: daemonDown(), podman: healthy() });
const config = await loadSandboxConfig({}, { sandbox: true });
expect(config?.command).toBe('podman');
// Pin the probe argument at the call site as well: `docker version` is what
// reaches the daemon, and it is the reason the fallback fires at all.
expect(spawnSync).toHaveBeenCalledWith(
'docker',
['version'],
expect.objectContaining({ timeout: expect.any(Number) }),
);
});
it('treats a non-zero exit with no output as broken and falls through', async () => {
// Pins the `?? synthesized message` fallback: with empty output the probe
// must still report a failure so selection moves on. Drop the fallback and
// probeSandboxCommand returns undefined here, docker is called usable, and
// the original bug returns with every selection assertion still green.
installed('docker', 'podman');
probes({ docker: brokenSilently(), podman: healthy() });
const config = await loadSandboxConfig({}, { sandbox: true });
expect(config?.command).toBe('podman');
});
it('probes each runtime once and reuses the result across calls', async () => {
// Selection runs more than once per startup (the sandbox hop, then again
// inside loadCliConfig), so without the cache a wedged runtime pays the
// timeout on every pass. Two selections must probe docker only once.
installed('docker', 'podman');
probes({ docker: healthy() });
await loadSandboxConfig({}, { sandbox: true });
await loadSandboxConfig({}, { sandbox: true });
const dockerProbes = spawnSync.mock.calls.filter(
([cmd]) => cmd === 'docker',
).length;
expect(dockerProbes).toBe(1);
});
it('still prefers docker when it is usable', async () => {
installed('docker', 'podman');
probes({ docker: healthy(), podman: healthy() });
const config = await loadSandboxConfig({}, { sandbox: true });
expect(config?.command).toBe('docker');
});
it('names the runtime that broke when no installed runtime can run', async () => {
installed('docker');
probes({ docker: daemonDown() });
await expect(loadSandboxConfig({}, { sandbox: true })).rejects.toThrow(
/docker.*cannot run.*Cannot connect to the Docker daemon/s,
);
});
it('names the first broken runtime when every installed runtime fails', async () => {
// Pins that the error reports docker (tried first), not podman (tried
// last). Flip `firstFailure ??=` to `=` and it would name podman with the
// suite otherwise green, sending the user to debug the wrong daemon.
installed('docker', 'podman');
probes({ docker: daemonDown(), podman: daemonDown() });
const error = await loadSandboxConfig({}, { sandbox: true }).catch(
(e: Error) => e,
);
const message = (error as Error).message;
expect(message).toContain("'docker'");
expect(message).not.toContain("'podman'");
});
it('treats a failure of only control characters as broken, not usable', async () => {
// The runtime exits non-zero but its output is nothing but escape/control
// bytes, which strip to ''. That empty string must not read as "no
// failure" — otherwise the broken runtime is selected, reintroducing the
// presence-vs-liveness bug through the sanitizer.
installed('docker', 'podman');
probes({
docker: { status: 1, stdout: '', stderr: '\x1b[0m\x07\n' },
podman: healthy(),
});
const config = await loadSandboxConfig({}, { sandbox: true });
expect(config?.command).toBe('podman');
});
it('strips ANSI and control characters from the runtime failure', async () => {
// The runtime's stderr is interpolated into a FatalSandboxError that
// reaches the terminal, so its escape and control bytes must not survive.
process.env['QWEN_SANDBOX'] = 'docker';
installed('docker');
probes({
docker: {
status: 1,
stdout: '',
stderr: '\x1b[31mCannot connect to the daemon\x1b[0m\x07\n',
},
});
const error = await loadSandboxConfig({}, {}).catch((e: Error) => e);
const message = (error as Error).message;
expect(message).toContain('Cannot connect to the daemon');
expect(message).not.toContain('\x1b');
expect(message).not.toContain('\x07');
});
it('surfaces the timeout error when a probe is killed at the cap', async () => {
// Pins the `result.error` branch — the wedged-daemon path the timeout
// exists for. Delete that branch and the throw degrades from the ETIMEDOUT
// text to "exited with null" with the suite still green.
process.env['QWEN_SANDBOX'] = 'docker';
installed('docker');
probes({ docker: timedOut() });
await expect(loadSandboxConfig({}, {})).rejects.toThrow(/ETIMEDOUT/);
});
it('does not blame QWEN_SANDBOX when --sandbox enabled the auto-detect path', async () => {
installed('docker');
probes({ docker: daemonDown() });
const failure = await loadSandboxConfig({}, { sandbox: true }).catch(
(error: Error) => error,
);
expect((failure as Error).message).toContain("'docker' is installed");
expect((failure as Error).message).toContain('--sandbox');
expect((failure as Error).message).not.toContain('QWEN_SANDBOX is true');
});
it('says QWEN_SANDBOX is true when the env var enabled the sandbox', async () => {
process.env['QWEN_SANDBOX'] = 'true';
installed('docker');
probes({ docker: daemonDown() });
await expect(loadSandboxConfig({}, {})).rejects.toThrow(
/QWEN_SANDBOX is true and 'docker' is installed but cannot run/,
);
});
it('keeps the generic message when nothing is installed at all', async () => {
installed();
probes({});
await expect(loadSandboxConfig({}, { sandbox: true })).rejects.toThrow(
/failed to determine command for sandbox/,
);
});
it('does not silently override an explicit QWEN_SANDBOX choice', async () => {
process.env['QWEN_SANDBOX'] = 'docker';
installed('docker', 'podman');
probes({ docker: daemonDown(), podman: healthy() });
await expect(loadSandboxConfig({}, {})).rejects.toThrow(
/'docker' \(from QWEN_SANDBOX\) is installed but cannot run/,
);
});
it('does not blame QWEN_SANDBOX for a command that came from --sandbox', async () => {
installed('docker', 'podman');
probes({ docker: daemonDown(), podman: healthy() });
// `--sandbox docker` / `tools.sandbox` reach the same code path, so the
// error must not point at an env var the user never set.
const failure = await loadSandboxConfig({}, { sandbox: 'docker' }).catch(
(error: Error) => error,
);
expect((failure as Error).message).toContain("'docker' is installed");
expect((failure as Error).message).not.toContain('QWEN_SANDBOX');
});
it('names QWEN_SANDBOX when a missing command really did come from it', async () => {
process.env['QWEN_SANDBOX'] = 'podman';
installed('docker');
probes({});
await expect(loadSandboxConfig({}, {})).rejects.toThrow(
/Missing sandbox command 'podman' \(from QWEN_SANDBOX\)/,
);
});
it('accepts an explicit choice that is usable', async () => {
process.env['QWEN_SANDBOX'] = 'podman';
installed('podman');
probes({ podman: healthy() });
const config = await loadSandboxConfig({}, {});
expect(config?.command).toBe('podman');
});
it('selects seatbelt on darwin without probing a daemon', async () => {
platform.mockReturnValue('darwin');
installed('sandbox-exec', 'docker');
probes({});
const config = await loadSandboxConfig({}, { sandbox: true });
expect(config?.command).toBe('sandbox-exec');
expect(spawnSync).not.toHaveBeenCalled();
});
it('returns undefined when the sandbox is disabled', async () => {
installed('docker');
probes({});
const config = await loadSandboxConfig({}, { sandbox: false });
expect(config).toBeUndefined();
expect(spawnSync).not.toHaveBeenCalled();
});
});

View file

@ -5,8 +5,12 @@
*/
import type { SandboxConfig } from '@qwen-code/qwen-code-core';
import { FatalSandboxError } from '@qwen-code/qwen-code-core';
import {
FatalSandboxError,
stripAnsiAndControl,
} from '@qwen-code/qwen-code-core';
import commandExists from 'command-exists';
import { spawnSync } from 'node:child_process';
import * as os from 'node:os';
import { getPackageJson } from '../utils/package.js';
import type { Settings } from './settings.js';
@ -28,6 +32,83 @@ function isSandboxCommand(value: string): value is SandboxConfig['command'] {
return (VALID_SANDBOX_COMMANDS as readonly string[]).includes(value);
}
// A healthy `docker version` answers in roughly 200-500ms, so this is already
// an order of magnitude of headroom. Keeping it tight matters because a wedged
// daemon blocks startup for the full cap.
const SANDBOX_PROBE_TIMEOUT_MS = 5_000;
// `loadSandboxConfig` runs twice on a sandboxed startup — once for the sandbox
// hop and once inside loadCliConfig — so selection is entered more than once
// per process. Cache each command's probe outcome so a runtime is contacted at
// most once; otherwise the wedged-daemon-then-fallback case pays the timeout
// twice. Daemon state changing mid-startup is not worth serving. Mirrors the
// ripgrep health cache (`ripgrepUtils.ts`).
const probeCache = new Map<SandboxConfig['command'], string | undefined>();
/** Clears the per-process probe cache so tests stay hermetic. */
export function resetSandboxProbeCacheForTest(): void {
probeCache.clear();
}
/**
* Confirms that a sandbox command can actually run, not merely that it is on
* PATH. A present container CLI is not a usable one: Docker Desktop may be
* stopped, the daemon may be unreachable, or the user may not be in the
* `docker` group. `version` is the cheapest command that still contacts the
* daemon, so it fails exactly when the runtime would fail later.
*
* `sandbox-exec` is a kernel facility rather than a daemon-backed client, so
* its presence on PATH is already sufficient.
*
* @returns The failure output when the command cannot run, or undefined when it
* is usable. The result is cached per command for the process.
*/
function probeSandboxCommand(
command: SandboxConfig['command'],
): string | undefined {
if (command === 'sandbox-exec') {
return undefined;
}
if (probeCache.has(command)) {
return probeCache.get(command);
}
const failure = runSandboxProbe(command);
probeCache.set(command, failure);
return failure;
}
function runSandboxProbe(
command: SandboxConfig['command'],
): string | undefined {
try {
const result = spawnSync(command, ['version'], {
encoding: 'utf8',
stdio: 'pipe',
timeout: SANDBOX_PROBE_TIMEOUT_MS,
});
if (result.error) {
return result.error.message;
}
if (result.status === 0) {
return undefined;
}
const output = `${result.stderr ?? ''}\n${result.stdout ?? ''}`;
const firstLine = output
.split('\n')
.map((line) => line.trim())
.find((line) => line.length > 0);
// The runtime's own output reaches a FatalSandboxError message, so strip
// ANSI/control characters from that untrusted string before it hits the
// terminal. Check for emptiness AFTER stripping: a line that is only
// control characters strips to '', which is falsy — return that and the
// caller reads the broken runtime as usable, the very bug this guards.
const stripped = firstLine ? stripAnsiAndControl(firstLine).trim() : '';
return stripped || `'${command} version' exited with ${result.status}`;
} catch (error) {
return error instanceof Error ? error.message : String(error);
}
}
function getSandboxCommand(
sandbox?: boolean | string,
): SandboxConfig['command'] | '' {
@ -50,6 +131,12 @@ function getSandboxCommand(
return '';
}
// An explicitly named command can come from QWEN_SANDBOX, --sandbox, or
// tools.sandbox in settings. Naming the wrong one sends the user looking in
// a place they never configured, so only claim the env var when it won.
const sandboxSource =
environmentConfiguredSandbox.length > 0 ? ' (from QWEN_SANDBOX)' : '';
if (typeof sandbox === 'string' && sandbox) {
if (!isSandboxCommand(sandbox)) {
throw new FatalSandboxError(
@ -60,28 +147,69 @@ function getSandboxCommand(
}
// confirm that specified command exists
if (commandExists.sync(sandbox)) {
// An explicit choice is never silently overridden — but it is still
// probed, so the failure names the runtime instead of surfacing later as
// an opaque container error.
const failure = probeSandboxCommand(sandbox);
if (failure) {
throw new FatalSandboxError(
`Sandbox command '${sandbox}'${sandboxSource} is installed but cannot run: ${failure}`,
);
}
return sandbox;
}
throw new FatalSandboxError(
`Missing sandbox command '${sandbox}' (from QWEN_SANDBOX)`,
`Missing sandbox command '${sandbox}'${sandboxSource}`,
);
}
// look for seatbelt, docker, or podman, in that order
// for container-based sandboxing, require sandbox to be enabled explicitly
const candidates: Array<SandboxConfig['command']> = [];
if (os.platform() === 'darwin' && commandExists.sync('sandbox-exec')) {
return 'sandbox-exec';
} else if (commandExists.sync('docker') && sandbox === true) {
return 'docker';
} else if (commandExists.sync('podman') && sandbox === true) {
return 'podman';
candidates.push('sandbox-exec');
}
if (sandbox === true) {
candidates.push('docker', 'podman');
}
// Selecting on presence alone would stop at an installed-but-unusable
// runtime and leave a working one below it unreachable, so each candidate is
// probed and the first one that actually runs wins.
let firstFailure: { command: string; detail: string } | undefined;
for (const candidate of candidates) {
if (!commandExists.sync(candidate)) {
continue;
}
const failure = probeSandboxCommand(candidate);
if (!failure) {
return candidate;
}
firstFailure ??= { command: candidate, detail: failure };
}
// throw an error if user requested sandbox but no command was found
if (sandbox === true) {
// Sandboxing can be switched on by the env var, by --sandbox, or by
// settings, so these messages name the env var only when it was the one
// that enabled it — same reasoning as sandboxSource above.
const enabledLabel = sandboxSource
? 'QWEN_SANDBOX is true'
: 'Sandbox is enabled';
const specifyHint = sandboxSource
? 'specify command in QWEN_SANDBOX'
: 'specify command via --sandbox or QWEN_SANDBOX';
// Report the runtime that actually broke rather than a generic
// "nothing installed", which would send the user down the wrong path.
if (firstFailure) {
throw new FatalSandboxError(
`${enabledLabel} and '${firstFailure.command}' is installed but cannot run: ` +
`${firstFailure.detail}; start it, try another installed runtime, or ${specifyHint}`,
);
}
throw new FatalSandboxError(
'QWEN_SANDBOX is true but failed to determine command for sandbox; ' +
'install docker or podman or specify command in QWEN_SANDBOX',
`${enabledLabel} but failed to determine command for sandbox; ` +
`install docker or podman or ${specifyHint}`,
);
}