Hey all. I’m trying to run pact-go in docker in our CI/CD, but I’m having issues building the container in CI. The plan is to create a test binary in an initial build stage, and then copy that binary alone into the next stage to keep the image size down. So in the build stage, I’m downloading and unzipping the FFI library into the correct location, but when I then try to build the binary, pact-go seems to have issues with finding the library that cause the build to fail. There’s no other obvious setup thats mentioned on the github, has anyone else had any success in getting a docker image built with pact-go?

Mind sharing the Dockerfile? I can take a look for you

# syntax=docker/dockerfile:1

FROM europe-docker.pkg.dev/management1c0c88c4/oci/go:latest AS builder
USER root

ARG NAME
ARG VERSION=unknown
ARG GITHUB_AUTH_TOKEN

ENV VERSION=$VERSION
ENV GITHUB_AUTH_TOKEN=$GITHUB_AUTH_TOKEN
ENV GOOUT=.

COPY . .

RUN \
wget <https://github.com/pact-foundation/pact-reference/releases/download/libpact_ffi-v0.4.0/libpact_ffi-linux-x86_64.so.gz>
RUN gunzip libpact_ffi-linux-x86_64.so.gz
RUN mv libpact_ffi-linux-x86_64.so /usr/local/lib/libpact_ffi.so
RUN ldconfig /usr/local/lib/libpact_ffi.so

RUN \
  GOMODCACHE=/usr/src/.go/pkg/mod \
  go test -c ./internal/provider/mas


# Stage 2 - Copy binary from Build Stage
FROM pactfoundation/pact-cli:latest

COPY --from=builder /mas.test /go-tests

COPY --from=builder /pact/entrypoint.sh /go-tests

ENTRYPOINT ["/go-tests/entrypoint.sh"]

There’s still some stuff I’ve been playing around with in there, but this is the current state

ta

Haha yeah thought you’d struggle to replicate 😄 Okay let me take a gander at that package

I think so

Have you had any experience with running it in github actions? Part of the reason I am where I am is because there didn’t seem to be a clear way to generate the contract in one action, and then pass the contract into the CLI docker image in order to push it into the broker

oh right, then there is definitely a way to do that

Ya

I was about to question the whole enterprise of build stages, because I can’t see why that’s a good thing to do 😆

I am all ears]

Have you had any experience with running it in github actions? Part of the reason I am where I am is because there didn’t seem to be a clear way to generate the contract in one action, and then pass the contract into the CLI docker image in order to push it into the broker

so you just want to: 1. Run the pact tests 2. Publish the contract file In a single action, or must it be across multiple stages?

A single action in itself would be fine ye. Currently the test runs as part of the unit tests, but the pact one always fails because the lib isn’t installed iirc

Apologies, the latest version of that for the 2.x.x branch is https://github.com/pact-foundation/pact-go/blob/2.x.x/Makefile

Yeah I’ll see where I can get with this, thanks Matt. One last q, do these all run as part of a single action, or is it across multiple?

I run it as a single. There is usually no need to delay publishing the pact file. You could have it as a separate step in the pipeline (we do that in our examples, see howtoexamples) but that’s up to you

The Pact Broker/PactFlow is designed to have large amounts of duplicate pacts published - so just send it without fear. It’s our job to make it performant

Nice thanks Matt, really appreciate your help as always