meda
bb2de12bae
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).
65 lines
2.8 KiB
YAML
65 lines
2.8 KiB
YAML
name: 'Setup BuildKit (with labels)'
|
|
description: 'Idempotently start a labeled buildkitd container and point buildx at it via the remote driver. The default docker-container driver cannot set container labels, and the Docker API has no PATCH-labels for existing containers — so we manage the container ourselves and Watchtower/Dockhand see the labels.'
|
|
inputs:
|
|
container_name:
|
|
description: 'Name of the buildkitd container'
|
|
required: false
|
|
default: 'buildkitd'
|
|
image:
|
|
description: 'BuildKit image'
|
|
required: false
|
|
default: 'moby/buildkit:buildx-stable-1'
|
|
monitor_only:
|
|
description: 'Value for com.centurylinklabs.watchtower.monitor-only'
|
|
required: false
|
|
default: 'false'
|
|
dockhand_notify:
|
|
description: 'Value for dockhand.notify'
|
|
required: false
|
|
default: 'false'
|
|
cleanup:
|
|
description: 'Stop the buildkitd container after the job (idle cleanup; container restarts on demand on the next run)'
|
|
required: false
|
|
default: 'true'
|
|
network:
|
|
description: 'Docker network for the buildkitd container — MUST match the network the job containers run on, otherwise the name is unresolvable'
|
|
required: false
|
|
default: 'git_default'
|
|
port:
|
|
description: 'TCP port buildkitd listens on'
|
|
required: false
|
|
default: '8375'
|
|
|
|
runs:
|
|
using: 'composite'
|
|
steps:
|
|
- name: Start BuildKit container (with labels)
|
|
shell: bash
|
|
run: |
|
|
# Recreate if a stopped/old container exists (config drift, e.g. port
|
|
# mapping changes, would otherwise be skipped by the name guard).
|
|
# If it is already running with the right config, keep it (warm cache).
|
|
if [ "$(docker inspect -f '{{.State.Running}}' ${{ inputs.container_name }} 2>/dev/null)" != "true" ]; then
|
|
docker rm -f ${{ inputs.container_name }} >/dev/null 2>&1 || true
|
|
# NOTE: no -p publish needed — the job executor itself runs on the
|
|
# same docker network, so it reaches buildkitd by container DNS name.
|
|
# (127.0.0.1 inside the executor is its own loopback, NOT the host's.)
|
|
docker run -d --name ${{ inputs.container_name }} --privileged \
|
|
--network ${{ inputs.network }} \
|
|
--restart unless-stopped \
|
|
--label com.centurylinklabs.watchtower.monitor-only=${{ inputs.monitor_only }} \
|
|
--label dockhand.notify=${{ inputs.dockhand_notify }} \
|
|
${{ inputs.image }} --addr tcp://0.0.0.0:${{ inputs.port }}
|
|
fi
|
|
|
|
- name: Set up Docker Buildx
|
|
uses: docker/setup-buildx-action@v4
|
|
with:
|
|
driver: remote
|
|
endpoint: tcp://${{ inputs.container_name }}:${{ inputs.port }}
|
|
|
|
- name: Stop BuildKit (idle cleanup)
|
|
if: ${{ inputs.cleanup == 'true' && always() }}
|
|
shell: bash
|
|
run: docker stop ${{ inputs.container_name }} || true
|