Summary
The user is seeking guidance on building the workload-launcher image with amd64 architecture on a Mac M1 machine.
Question
Hi all - I am trying to build the workload-launcher image from the airbyte-platform repository but I am not sure how can I build it with amd64 architecture while running it on Mac M1 - Any hints on how can I accomplish this?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
["building", "workload-launcher", "amd64-architecture", "mac-m1", "airbyte-platform"]
Hey Dabek, thank you for chiming in! 
I am looking for something more related to the gradle files from Airbyte. As I see there is the Build step, which generated the airbyte-app.tar and glues it together with the Dockerfile, but it creates it using my machine architecture (arch64).
I tried but running step “distTar” and copying the .tar into the folder where the Dockerfile is and ran “docker buildx build --platform linux/amd64 -t private-repo/airbyte/workload-launcher:1.1.0 .” - This works, however this is a very mechanical process and further I think there are missing steps with this approach as later on when deploying this image I find on the pods logs:
p11-kit: couldn't create file: /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt: Unknown error 30
p11-kit: couldn't create file: /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem: Unknown error 30
I am running the pods with no privileges and readonly filesystem so this error is somehow expected if you run update-ca-trust from the pod (I am pressuming that is the command it is running), but the original image from docker hub does not have this problem