deployer: resolve relative socket path via AbsSocketPath #654

Open
opened 2026-08-13 14:31:53 +00:00 by the.auditor · 0 comments
Owner

cmd/thwap-pagesd/main.go passes cfg.Standalone.SocketPath straight to docker.NewClient, which builds unix://+path. A relative socket_path (e.g. ./docker.sock) becomes unix://./docker.sock and fails. The unused docker.AbsSocketPath helper (added in #642) resolves relative paths; wire it into newDeployer (or require an absolute path) so rootless/relative socket setups work.

See PR #652.

`cmd/thwap-pagesd/main.go` passes `cfg.Standalone.SocketPath` straight to `docker.NewClient`, which builds `unix://`+path. A relative `socket_path` (e.g. `./docker.sock`) becomes `unix://./docker.sock` and fails. The unused `docker.AbsSocketPath` helper (added in #642) resolves relative paths; wire it into `newDeployer` (or require an absolute path) so rootless/relative socket setups work. See PR #652.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
thwap/thwap-pagesd#654
No description provided.