Closed holdenk closed 1 month ago
I also have this issue. Thanks for raising it @holdenk .
any news?
any news?
any news?
Hey there, adding my 2 cents here, because I just got it working. It looks like this has no more support so I'll tell you the steps I did to get it working
GOARCH=amd64
to GOARCH=arm64
.docker buildx build --platform linux/arm64 --build-arg SPARK_IMAGE=apache/spark:v3.2.2 -t your-repo/your-image:v3.2.2-arm .
I'm currently testing that no problems arise from this, but it seems like these are the only change requirements. Then update the values of the helmchart to use this image and that should be it.
@gonzalezzfelipe I've done so, and I'm getting the following error once container is started:
exec: "/usr/bin/entrypoint.sh": permission denied: unknown
@mfidemraizer,
I was just working on this trying to deploy spark operator on an AWS Graviton cluster. After successfully building the image and attempting to run the container on docker desktop, I got the same error as you:
To fix this issue, I added a new RUN
line to my dockerfile that changes the permissions of the entrypoint.sh
file and was able to initialize the container successfully:
COPY spark-operator/entrypoint.sh /usr/bin/
RUN chmod +x /usr/bin/entrypoint.sh
ENTRYPOINT ["/usr/bin/entrypoint.sh"]
tested spark 3.5.0 on RPi microk8s today using docker image and can confirm it is working fine by following the instructions above.
Given that #1735 would likely be solved by an arm64 image, is there any reason the project does not publish arm64 images?
I'm new to this community, but it looks like the arm64 image of spark-operator has been available on Docker Hub for a while. I have successfully run the operator, webhook, and spark driver/exec pods on AWS graviton instances.
/close
The images are built for both amd64 and arm64 in the release workflow.
@jacobsalway: Closing this issue.
Given the proliferation of arm based cloud instances and the nvidia arm platforms it would make sense to support running on arm64.