-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build linux/arm64 images #51
base: master
Are you sure you want to change the base?
Conversation
99c5bdd
to
0a205c3
Compare
@vitalif Hi, it would be great if you could take a look at this patch and possibly merge it. Thanks! |
Hi, why did you remove local makefile? I want to be able to build it locally without github ci. |
I also think that arm64 csi-s3 can be built without qemu at all because Go allows for very easy cross compilation |
0a205c3
to
9e36d40
Compare
I thought it would be verbose because everything can be built on GitHub Actions, but I guess it's helpful to keep it so you can test it (and publish it) locally.
You're right! This also drastically reduces build time, thanks for the suggestion. |
b1b4a70
to
e000550
Compare
@vitalif Hi, I fixed the patch following your comments. Would you take a look at this again? |
e000550
to
fc23e42
Compare
Sorry that you have to wait, I think your PR is fine, but I wasn't sure about the multi-architecture support in Yandex container registry. It seems it's not supported yet. So for now it won't work :) Container registry team says they are already working on a fix, so I'll merge it when it is ready. |
Thanks for the update! I'm glad to hear that. I'm in no rush, looking forward to it. |
@vitalif Sorry for pushing, however, do we have an update on this yet? Is there anything we could assist with? The lack of arm64 is currently blocking me to continue my research 😞. |
Hi. No, container registry support for "fat manifests" is not rolled out yet. I suppose you can use your own builds by now?) |
@vitalif Yes, I was able to do so. However following images need to be also upgraded (no arm support): k8s-csi-s3/deploy/kubernetes/csi-s3.yaml Lines 47 to 51 in 4e410df
Here we need to use image:
k8s-csi-s3/deploy/kubernetes/provisioner.yaml Lines 77 to 80 in 4e410df
And here also:
Anyways |
fc23e42
to
5ea1854
Compare
6fbc8c9
to
227e1cf
Compare
5ea1854
to
a419999
Compare
any update on this ? |
Any updates? |
a419999
to
0f5dca8
Compare
I'd also love to use this, how's the status? Could pushing the multi-platform version to for example GHCR be an interim solution? |
0f5dca8
to
7ffbc6b
Compare
@motoki317 THANK YOU SOOOOO MUCH I JUST FINISHED TETING IT ALLLL AND IT WORKKSSSS on arm64 i run jupyterhub with that csi driver now with my own minio its just the heavennssss AWESOMEEE I really mean the THANK YOU I had to trick around more things after that because i needed the official csi images like the registrar on ARM64 too, but i could easily find some from different companies on dockr hub with arm64 support, wow its really awesome ! without your work would have been muchhh harder! |
@Jean-Baptiste-Lasselle I’m glad you found it useful :) Yes, you do need to swap some more CSI default images from what is provides in this repository, see the PR description and their latest versions to see how I did it. We should probably update those as well, maybe in another commit or PR. |
Is this still being worked on? |
What about this PR, won't it support ARM? |
I've partially added support for this in #145 |
@vitalif Hi, it's been a while, any update on this? It looks like a few other people also want this PR merged. |
Hello,
I noticed that there is no multiplatform support of the driver image, and I thought it'd be nice to have the image built for both linux/amd64 and linux/arm64 platforms.
This change utilizes docker actions to build multiplatform images, which replaces old script in Makefile.
I tested it in my own arm64 environment on OCI A1 instance, it seems to be working.
ref: package, manifest (values.yaml)
Thank you in advance.