Building Airbyte Docker image with custom architecture

Summary

The user is trying to build an Airbyte Docker image with a custom architecture using gradle files. They are facing issues with missing steps and encountering errors related to file creation when deploying the image.


Question

Hey Dabek, thank you for chiming in! :slightly_smiling_face:
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



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

["gradle-files", "build-step", "dockerfile", "architecture", "docker-image", "custom-architecture", "pods", "error"]