mmoscher commented on issue #686: URL: https://github.com/apache/solr-operator/issues/686#issuecomment-1942415528
@fliphess yes ya totally right. We're running the zookeeper-operator as well. Just double-checked our local deployment. Colima spawns - when running with k3s - an aarch64 instance as default (which should be the same as arm64). However the mac virtualization does some magic as well. Zookeeper itself claims to be running in amd64: <img width="953" alt="image" src="https://github.com/apache/solr-operator/assets/2553753/4a59426e-27d8-4953-b92d-12c585031881";> Didn't know this yet, learned something new today 😆 . Need to double-check this tomorrow. This, however, explains why we do not have any issues running our deployment locally on m1/m2 macs. Nevertheless, 2 years ago - when prepping for the macs to arrive - I managed to get up and running our local deployment on a GCP [Tau T2A instance](https://cloud.google.com/compute/docs/general-purpose-machines#t2a_machines). Thus, I was able to run the zookeeper-operator on ARM. So you should be able to use my branch/fork for it. Feel free to contribute back any changes/fixers you need to make on the way. Maybe it will be merged upstream any time soon. Keep in mind that need to build both, the operator and the zookeeper image itself. Furthermore, keep in mind that you need to have buildx with qmeu in-place or you have to run your builds directly in the graviton machines. My wrapper script to perform the build was the following: ```bash #!/usr/bin/env bash set -e pushd "/tmp" echo "[INFO] Building zookeeper operator ..." git clone [email protected]:mmoscher/zookeeper-operator.git && pushd "zookeeper-operator" TAG=0.2.14 REPO=your-repo/zookeeper docker buildx build \ --push \ --build-arg VERSION=$TAG \ --platform=linux/amd64,linux/arm64 \ -t ${REPO}-operator:$TAG \ . docker buildx build \ --push \ --build-arg VERSION=$TAG \ --platform=linux/amd64,linux/arm64 \ -t ${REPO}:$TAG \ ./docker popd rm -rf zookeeper-operator echo "[INFO] zookeeper operator done ..." ``` Hf 🍻 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
