Bryan Helmkamp 97f74c3ab0 Forward the Docker daemon selection and Daytona credentials to Petri workers ... A Petri run's worker launches the sandbox-driver plugins itself, and the Docker plugin forwards `DOCKER_HOST`, `DOCKER_TLS_VERIFY`, `DOCKER_CERT_PATH`, `DOCKER_API_VERSION`, `DOCKER_CONFIG` and `DOCKER_CONTEXT` from the process that launches it. They now cross the worker's environment allowlist, so the worker's sandboxes go to the daemon the server uses. The concern that kept them out, the legacy worker's own Docker client picking up a daemon it was not meant to, is moot: the legacy executor is being deleted. The same variables pass through the test harness's isolation, so a developer's daemon selection reaches the servers tests start. Daytona's non-secret selectors, `DAYTONA_API_URL` and `DAYTONA_ORGANIZATION_ID`, cross the allowlist too. The API key stays the vault's: a Daytona run's worker command carries it the way the GitHub app key travels, and the Daytona plugin reads it from the worker's process. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-18 09:10:29 -04:00
..
src	Forward the Docker daemon selection and Daytona credentials to Petri workers	2026-09-18 09:10:29 -04:00
Cargo.toml	refactor: organize crates into three layers	2026-07-23 17:59:34 -04:00