mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-10-01 02:04:24 +00:00
97f74c3ab0
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> |
||
|---|---|---|
| .. | ||
| build-support | ||
| fabro-api | ||
| fabro-auth | ||
| fabro-client | ||
| fabro-config | ||
| fabro-core | ||
| fabro-db | ||
| fabro-dev | ||
| fabro-http | ||
| fabro-macros | ||
| fabro-oauth | ||
| fabro-options-metadata | ||
| fabro-proc | ||
| fabro-redact | ||
| fabro-static | ||
| fabro-telemetry | ||
| fabro-template | ||
| fabro-test | ||
| fabro-types | ||
| fabro-util | ||
| fabro-vault | ||