• v32.21.1
    Release / build-and-release (push) Failing after 11m55s
    Stable

    philkunz released this 2026-09-29 10:05:27 +00:00 | 88 commits to main since this release

    2026-09-29 - 32.21.1

    Fixes

    • Reach the Docker daemon again from the release binary. Onebox 32.21.0, the first release built with Deno 2.9.7, could not open the Docker socket: every Docker API request failed with invalid proxy url, so the daemon crash-looped at start with Failed to initialize Docker client: invalid proxy url. @push.rocks/smartrequest up to 5.5.0, which @apiclient.xyz/docker sends every request through, opened a Unix socket through the undocumented Deno.createHttpClient({ proxy: { url: 'unix://…' } }), which Deno 2.9.6 and later reject; 5.5.1 uses Deno's typed { transport: 'unix', path } proxy. @apiclient.xyz/docker moves from 9.2.0 to 10.1.1, which requires smartrequest ^5.5.1, in package.json, pnpm-lock.yaml and the binary's deno.lock, and both locks now resolve the single smartrequest 5.5.1 (from 5.0.4), keeping the sha512 integrity of every package and the lock's registry origin. Onebox reads no network IPAM or Labels, which 10.0.0 types as nullable, and never calls activateSwarm(), which rejects since 10.1.0, so no Onebox code changes with it; 9.3.0 addresses every absolute Unix socket path, /var/run/docker.sock included, as before.
    • The test suites and the binary check could not see this: Node takes smartrequest's Node transport, and the binary check ran only --version and the Typed RPC self-test, neither of which opens the Docker socket. The new onebox selftest docker reads the engine version through the Docker API client every Onebox Docker manager uses, from the daemon DOCKER_HOST names or else /var/run/docker.sock, and constructs nothing else. pnpm run verify:binary, which build:binary and the release workflow run, now starts a fake Docker API on a temporary Unix socket, runs the compiled x64 binary's selftest docker against it and requires the pass line and both the /_ping and /version requests to arrive; it fails with invalid proxy url on a binary built with smartrequest 5.0.4. Every binary run of the check is now bounded to 120 seconds.
    Downloads