docker-superset icon indicating copy to clipboard operation
docker-superset copied to clipboard

Published 20 hours ago • verified publisher icon amancevice

Add support of ARM architecture

Open sadmin91 opened this issue 4 years ago • 7 comments

I'm using your container definition on my raspberry Pi. To doing this, I have change the base image of your Dockerfile from python to arm32v7/python.

Do you think is possible to add this modification on this repo ?

sadmin91 avatar May 03 '20 15:05 sadmin91

I don't know much about raspberry pi, but I have to think it would be a big challenge given the number of dependencies of this project. There could be some C-library incompatibilities off the top of my head.

amancevice avatar May 05 '20 13:05 amancevice

I don't think that this support of ARM architecture will be a big challenge. Only one modification on Dockfile is needed on my side. But maybe i'm wrong.

sadmin91 avatar May 06 '20 15:05 sadmin91

I don't think I'd want to be responsible for maintaining something I don't fully understand (it's just me over here, I'm not affiliated with Superset). But what I could do is variable-ize the base image for each stage so you could build the image yourself with whatever base you wanted.

Ex:

docker build \
  --build-arg FINAL_BASE=arm32v7/python \
  --tag sadmin91/superset \
  https://github.com/amancevice/docker-superset.git

Would that work for you?

amancevice avatar May 07 '20 13:05 amancevice

The support issue of ARM is not about docker, the key point is that pyarrow has issue on ARM, and after Superset-0.34 pyarrow becomes a requirement of Superset. You can't solve this easily on the docker side. However, you can use some legacy version of Superset or docker of Superset on Raspbian, such as Superset 0.34.0. This version could run successfully on my Raspberrypi 4.

tierzhang avatar May 08 '20 03:05 tierzhang

It looks like the pyarrow issue has been solved in superset: https://github.com/apache/superset/pull/14891

Given the increasing prevalence of ARM since this issue was opened (locally on M1s; Graviton on AWS, etc), it may be worth revisting this?

davidbodow-st avatar Aug 07 '23 13:08 davidbodow-st

I’m happy to consider this but it will require setting up a bit of CI/CD infrastructure to build the images—AFAIK GitHub actions doesn’t support anything but x86

amancevice avatar Aug 09 '23 10:08 amancevice

Actually, turns out Docker has some docs on doing this. I'll explore that a bit today

amancevice avatar Aug 09 '23 15:08 amancevice

I saw arm here, it worked, but now again only amd... Any chances to get ARM?

image

mmospanenko avatar Jan 28 '24 16:01 mmospanenko

Just merged a change to the GitHub release workflow to target both linux/amd64 and linux/arm64 when building/pushing.

amancevice avatar Feb 04 '24 18:02 amancevice

closing this out as I think it is accomplished, feel free to re-open or file a new issue if you disagree

amancevice avatar Feb 05 '24 17:02 amancevice