-
Notifications
You must be signed in to change notification settings - Fork 440
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
Add arm64v8 image #12
Comments
I installed successfully k3s on arm64 with weave Net overlay network on a bunch of RockPro64 hexa-core cluster and made my own private local-path-provisioner arm64v8 instance using Alpine Linux instead of Ubuntu:18.04. Alpine Linux image size is approx 100Mi, testing was successful.
IMHO alpine linux reduce the footprint even further.
Should I make a PR using Alpine Linux? |
@giminni Sure, that would be great! Though I don't have a setup to test arm64, so I would be unable to fix if there is anything wrong with Arm. But I am OK on accepting a PR for arm64 as long as there is no impact on running with x86. |
@giminni we switched to Alpine in #13 , I think adding arm64/multi-arch support can build off that potentially? I'm not sure why the |
have any arm images been pushed anywhere? |
Can anyone try @km4rcus 's image? The build has been merged to master as well. |
@yasker can you initiate a build to docker hub? |
I haven't tried that specific build but I did build it for arm myself and it is working |
v0.0.8 released and the image pushed. Let me know if it works. |
@yasker I don't see any multi-arch image tags on docker hub and also no manifest to support multi-arch |
@vchrisb sorry, not familiar with multi arch build. Let me check what should I do for an arm image. |
@yasker , please take a look at |
|
@tamsky Thanks for the help! I will check it. |
Can we /reopen this ticket as it is still waiting for #24 to be merged? |
Multiarch supported in v0.0.11 release. https://github.com/rancher/local-path-provisioner/releases/tag/v0.0.11 |
adding arm64v8 support would be great!
The text was updated successfully, but these errors were encountered: