-
Notifications
You must be signed in to change notification settings - Fork 191
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
v0.14.0 not starting on k8s v1.20.2 and ARM64 #385
Comments
It is probably related to ARM64 and the ARMv7 issues we experienced, I even think there is a chance that the ARMv7 patch conflicts with ARM64. Do you by any chance make use of the automation controllers? If so, do they boot OK (image-automation-controller in particular)? |
Yes I use them, and |
That gives me sufficient information to look for a solution, or rather, trace why the image-automation-controller succeeds to build without the patch that was required for this controller. This may take some time, but I'll start tomorrow. |
In the meantime: dropping the |
Thank you! Let me know if you need anything from me or if I can assist you in some way. |
Same problem here on Kubernetes I have no starting log, the
|
Any chance one of you also has access to an ARMv7 machine? If so, can you please confirm the current image does work on that machine? |
I'm afraid I don't have access to an ARMv7 machine. |
Hi!
I upgraded to Flux v0.15.0 which includes the v0.14.0 of the source-controller. I can't get the pod to start, crashes immediately, no info in logs (tried both
error
anddebug
for log-level). I manually changed the image from v0.14.0 to v0.13.2 and it starts without any issues.Can this be related to ARM64? (I read some info in the release notes regarding some ARMv7 issues?)
It exits with exit code 139, no other info that I can find.
The text was updated successfully, but these errors were encountered: