@sagikazarmark I asked a similar question regarding building temporal with boringcrypto here: Building temporal with boringcrypto
Because our team already has a docker image which is based on alpine linux and installs the boringcrypto fork of golang, it was pretty straightforward to get this working.
I just needed to change this line in the temporal Dockerfile to use our custom alpine image (with the boringcrypto fork of golang installed) and then set CGO_ENABLED=1 here.
We haven’t done much testing with this build of temporal yet, but we are able to stand it up locally with the docker-compose-mysql file in the temporal repo and run some basic workflows against it. Building with the boringcrypto fork of golang and enabling cgo didn’t seem to cause any issues.