Skip to content
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

Should this run on arm64 please? #5

Closed
Digital-Daz opened this issue Jun 6, 2020 · 9 comments
Closed

Should this run on arm64 please? #5

Digital-Daz opened this issue Jun 6, 2020 · 9 comments

Comments

@Digital-Daz
Copy link

I have a cluster of Pi4s that I am trying to implement this on.

I just get crash loop backoff for all the pods.

The logs seem to indicate a problem with driver registrar container and maybe the cleanup container. I'm very, very new to all of this so I'm unsure.

kubectl logs democratic-csi-1591404995-node-w2tsd csi-driver
info: initializing csi driver: freenas-iscsi
info: starting csi server - name: org.democratic-csi.iscsi, version: 0.1.0, driver: freenas-iscsi, mode: node, csi version: 1.1.0, address: , socket: unix:///csi-data/csi.sock

kubectl logs democratic-csi-1591404995-node-w2tsd driver-registrar
standard_init_linux.go:211: exec user process caused "exec format error"

kubectl logs democratic-csi-1591404995-node-w2tsd cleanup
standard_init_linux.go:211: exec user process caused "exec format error"

TIA
Daz

@travisghansen
Copy link
Member

My code should be multi-arch however there are numerous other bits revolving around csi (all the ‘sidecar’ containers) that are not. There has been some movement recently though on several so I’m (as well as all other csi drivers) optimistic we’ll have them before long.

@Digital-Daz
Copy link
Author

Thanks for the quick reply. I'll see what I can do in the meantime to get some form of iscsi working.

@travisghansen
Copy link
Member

There is no upgrade path between the 2 projects but it would be pretty easy to run this: https://github.com/travisghansen/freenas-iscsi-provisioner

I’m not currently building arm images but an alternative is to simply run the provisioner out of the cluster (including potentially on FreeNAS itself). Arm images probably wouldn’t be too hard to build for that project but non-csi drivers are essentially dead.

@Digital-Daz
Copy link
Author

Digital-Daz commented Jun 7, 2020

Thank you, I'm just letting you know that I was able to successfully get this working by replacing the images form quay.io in the helm chart with ones from https://github.com/raspbernetes/multi-arch-images and also swapping the busybox image for the cleanup container to an arm64 one from docker.

The provisioner seems to be working perfectly.

@travisghansen
Copy link
Member

Oh wow! Can you share your yaml file (remove secrets obviously)? There are others that have been interested in running with arm and I can point them to this temporarily.

Thanks!

@Digital-Daz
Copy link
Author

Sorry for the delay, I only just noticed this.

This should be enough:
Archive.zip

@travisghansen
Copy link
Member

Thanks! I’ll take a look.

@travisghansen
Copy link
Member

Can you share your experiences so far after using it on arm for a bit?

@travisghansen
Copy link
Member

I've released a new version of the chart which fixes many things and allows for setting the images via values.yaml. Should make this easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants