meda bb2de12bae fix: use container DNS name endpoint, executor runs on same docker network ...

Root cause of the 'waiting for connection' build failure: the act_runner
executor container runs on the same docker network as buildkitd, so its
127.0.0.1 is its own loopback — the host-published port is unreachable
from there. Revert to tcp://<name>:<port>; container DNS resolves on the
shared network. Drop the now-useless loopback port publish.

Verified on host: from a container on that network, endpoint
tcp://<name>:8375 -> 'Status: running'; tcp://127.0.0.1:8375 ->
'ERROR: context deadline exceeded' (exact CI symptom).

2026-09-01 13:40:02 +02:00

action.yml

fix: use container DNS name endpoint, executor runs on same docker network

2026-09-01 13:40:02 +02:00

S

Description

No description provided

39 KiB