Console Builder as Multi-Arch Image

[Jdubrick]

Hello, we are currently using the tectonic-console-builder image as our builder for a Dockerfile here. I am currently on an M2 Mac and when trying to build an image from our Dockerfile using tectonic-console-builder as a base I am running into the following error log:

[1/2] STEP 1/7: FROM quay.io/coreos/tectonic-console-builder:v27 AS build
Trying to pull quay.io/coreos/tectonic-console-builder:v27...
Getting image source signatures
Copying blob sha256:b44909a43291f7d55264b942192d854b13c144ffcdadc9f206cf62a2f1840220
Copying blob sha256:ec335f17d0c74f7a270925cb1bbd29acc72ae904c6f4570f9ae369e3eebb64ed
Copying blob sha256:7f67b1746a83d257a6398cf8eec47bfa1f854670097ea4234f12857cfc7d5932
Copying blob sha256:fbd73e3517bc8fa1e9863e448b6ad3b54c5482345b15ce6ad28439cf1f017523
Copying blob sha256:d2b4675e1918dcb7f5c9bfedbb5a8634d2459306d1f3b91f08c7293380f10585
Copying blob sha256:158da8fc0167ae10e46bfdefe0ee48dbb11de01094a55a5b2f4f182588071590
Copying blob sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1
Copying blob sha256:0738ed3211221f456f33fcecfff4c6a131b04dd8ca6b29d39e7b49480bac9020
Copying blob sha256:84d778703f10141faf4ccec56b47f444e31ba8fd444c8bb7b0b3c5f9af86d5e7
Copying blob sha256:4b17b4295de593bc3a6c197e1db45979f4aa1833e564495f5027e541e02e58d6
Copying blob sha256:16eddb86b2a7522daad3e97aaf77cb62e770f309f5c49be2d4f6859378101d81
Copying blob sha256:b2be8dfe747575eb7dd8dc2bb7328af5e7d36e6862e35ffe4902a7a4b90bd94d
Copying blob sha256:af59bd041d3ae4daac79644465912034f0c500c1946e39484c105630b3bc7fab
Copying blob sha256:9f82f5fcb66a3668ead579b0e8d6ae6464ff977dbe2bdd89aa052c9d218a6ede
Copying blob sha256:cc2b59c2d67211e3b4d44ab2cdd18ed586e2fffe609e59c41b7b1cadf13ac32f
Copying blob sha256:2e41fac7a4a3b12b1a62beb7fdc20fd3d309fe5c6f054f0205f984bf339e3fa2
Copying config sha256:274004871d90fd2fc0de4eebcfa5871c971a20ec08d9fc423539ebfb1859f7e2
Writing manifest to image destination
WARNING: image platform (linux/amd64) does not match the expected platform (linux/arm64)
[1/2] STEP 2/7: RUN mkdir -p /go/src/github.com/openshift/
--> f2a118ab9c70
[1/2] STEP 3/7: RUN cd /go/src/github.com/openshift && git clone https://github.com/openshift/console.git
Cloning into 'console'...
Updating files: 100% (14012/14012), done.
--> 1e4d57a48551
[1/2] STEP 4/7: WORKDIR /go/src/github.com/openshift/console/
--> de0a7316e9a1
[1/2] STEP 5/7: RUN yarn config set ignore-engines true
yarn config v1.22.10
success Set "ignore-engines" to "true".
Done in 0.16s.
--> c2ad85c0de7f
[1/2] STEP 6/7: RUN yarn config set network-timeout 1000000 -g
yarn config v1.22.10
success Set "network-timeout" to "1000000".
Done in 0.16s.
--> ea5826f803f6
[1/2] STEP 7/7: RUN ./build.sh
/go/src/github.com/openshift/console/frontend /go/src/github.com/openshift/console
yarn install v1.22.22
[1/4] Resolving packages...
warning Resolution field "[email protected]" is incompatible with requested version "minimist@~0.0.1"
warning Resolution field "[email protected]" is incompatible with requested version "minimist@^1.2.8"
[2/4] Fetching packages...
warning Pattern ["asn1js@latest"] is trying to unpack in the same destination "/usr/local/share/.cache/yarn/v6/npm-asn1js-2.0.26-0a6d435000f556a96c6012969d9704d981b71251-integrity/node_modules/asn1js" as pattern ["asn1js@^2.0.26"]. This could result in non-deterministic behavior, skipping.
[3/4] Linking dependencies...
warning " > @patternfly/[email protected]" has incorrect peer dependency "showdown@>=2.1.0".
warning " > [email protected]" has incorrect peer dependency "[email protected] || ^15.0.0 || ^16.0.0".
warning " > [email protected]" has incorrect peer dependency "[email protected] || ^15.0.0 || ^16.0.0".
warning " > [email protected]" has incorrect peer dependency "react@^16.8.0".
warning " > [email protected]" has incorrect peer dependency "react@^15.3.0 || ^16.0.0".
warning " > [email protected]" has incorrect peer dependency "@types/react@^17.x".
warning " > [email protected]" has incorrect peer dependency "react@^16.0.0 || ^15.0.0 || ^0.14.0".
warning " > @cypress/[email protected]" has unmet peer dependency "@babel/preset-env@^7.0.0".
warning "@graphql-codegen/typescript > @graphql-codegen/visitor-plugin-common > @graphql-tools/relay-operation-optimizer > [email protected]" has incorrect peer dependency "graphql@^15.0.0".
warning " > @testing-library/[email protected]" has unmet peer dependency "@testing-library/dom@>=7.21.4".
warning "@wojtekmaj/enzyme-adapter-react-17 > [email protected]" has incorrect peer dependency "[email protected] || 0.14.x || ^15.0.0-0 || ^16.0.0-0".
warning "@wojtekmaj/enzyme-adapter-react-17 > enzyme-adapter-utils > [email protected]" has incorrect peer dependency "react@^0.14 || ^15.0.0 || ^16.0.0-alpha".
warning " > [email protected]" has unmet peer dependency "axe-core@^3 || ^4".
warning " > [email protected]" has incorrect peer dependency "cypress@^3 || ^4 || ^5 || ^6".
warning " > [email protected]" has unmet peer dependency "mocha@>=3.1.2".
warning " > [email protected]" has unmet peer dependency "mocha@>=2.2.5".
warning " > [email protected]" has unmet peer dependency "mocha@>=7".
warning " > [email protected]" has unmet peer dependency "[email protected] || 0.20.x".
warning " > [email protected]" has incorrect peer dependency "[email protected]".
warning "workspace-aggregator-7ebec5a2-4522-4703-a651-27c8fef8eb07 > eslint-plugin-console > [email protected]" has incorrect peer dependency "eslint-plugin-react-hooks@^1.7.0".
warning Workspaces can only be enabled in private projects.
warning Workspaces can only be enabled in private projects.
[4/4] Building fresh packages...
./build-frontend.sh: line 6: 12409 Segmentation fault      (core dumped) yarn install
Error: building at STEP "RUN ./build.sh": while running runtime: exit status 139

I found your script to build this image here and altered it to build for arm64, pushed it to my quay, and used that instead and the issue went away. I believe this error is related to emulation since I am on a different architecture. My team is trying to move to running some of our CI on graviton instances so we are migrating our image builds to support both amd64 and arm64. Is there any possibility for quay.io/coreos/tectonic-console-builder to be supported for multiple architectures? Namely linux/amd64 and linux/arm64?