Add arm64v8 image about local-path-provisioner HOT 16 CLOSED

Can we /reopen this ticket as it is still waiting for #24 to be merged?

from local-path-provisioner.

Multiarch supported in v0.0.11 release.

https://github.com/rancher/local-path-provisioner/releases/tag/v0.0.11

from local-path-provisioner.

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.

$ uname -a
Linux <server> 4.4.167-1161-rockchip-ayufan-g6f1664023387 #1 SMP Fri Mar 22 23:03:38 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux

$ k get all -n local-path-storage
NAME                                          READY   STATUS    RESTARTS   AGE
pod/local-path-provisioner-6868fbd6c6-nvjk5   1/1     Running   0          22m

NAME                                     READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/local-path-provisioner   1/1     1            1           22m

NAME                                                DESIRED   CURRENT   READY   AGE
replicaset.apps/local-path-provisioner-6868fbd6c6   1         1         1       22m

IMHO alpine linux reduce the footprint even further.

$ docker images
REPOSITORY                       TAG                 IMAGE ID            CREATED             SIZE
powder/local-path-provisioner   arm64v8-latest      4648cd96351c        39 minutes ago      84MB
multiarch/alpine                arm64-edge          5d8c30c02153        21 hours ago        15.9MB

Should I make a PR using Alpine Linux?

from local-path-provisioner.

@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.

from local-path-provisioner.

@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 local-path-provisioner:arm64v8 image is so much larger than plain alpine:arm64, however. When I cross-compiled the Go arm64 binary it was 27MB.

from local-path-provisioner.

have any arm images been pushed anywhere?

from local-path-provisioner.

Can anyone try @km4rcus 's image? The build has been merged to master as well.

from local-path-provisioner.

@yasker can you initiate a build to docker hub?

from local-path-provisioner.

I haven't tried that specific build but I did build it for arm myself and it is working

from local-path-provisioner.

v0.0.8 released and the image pushed. Let me know if it works.

from local-path-provisioner.

@yasker I don't see any multi-arch image tags on docker hub and also no manifest to support multi-arch
Did you update your build pipeline?

from local-path-provisioner.

@vchrisb sorry, not familiar with multi arch build. Let me check what should I do for an arm image.

from local-path-provisioner.

@yasker , please take a look at
https://github.com/rancher/dapper/blob/master/scripts/build
for a rancher-approved dapper-style example.

from local-path-provisioner.

arm image seems to be missing as well, this is what I got on a raspberry pi:

kubectl logs -n local-path-storage pod/local-path-provisioner-69fc9568b9-vg4m2
standard_init_linux.go:211: exec user process caused "exec format error"

from local-path-provisioner.

@yasker please take a look at #24 , thanks!

from local-path-provisioner.

@tamsky Thanks for the help! I will check it.

from local-path-provisioner.