Closed jagoe closed 3 years ago
Hi @jagoe, thanks for reaching out. Have you tried debugging in non-isolated mode (i.e. not requiring routingmanager)? Will that work for your scenario?
Hey, thanks for the quick reply.
Sadly, that results in the same issue with both lpkremoteagent
and lpkrestorationjob
.
@jagoe Sorry to hear that. As far as I know this isn't on our backlog yet, however I've made a note to discuss this with the team for future improvements. Out of curiosity, what specific issues are you seeing -- are the pods simply unable to come up, or do the logs show errors?
@amsoedal Alright, thanks for the feedback.
The pods crash, each logging this error: standard_init_linux.go:219: exec user process caused: exec format error
That's a pretty good sign the binaries aren't built for the architecture that tries to execute them.
I'm not in a hurry for that to work, since I was just playing around with the extension. I might try it again on a cluster with amd64 architecture next week.
Closing this issue due to inactivity. Please feel free to reopen if still valid. Thank you.
Hello, I'm facing the same problem, trying to run it on a k3s raspberry pi cluster (arm64) too, but lbkremoteagent
is crashing and goes to a CrashLoopBackOff
state, is it still not a wanted feature?
Hi @Titae, unfortunately we haven't prioritized the work to support ARM architectures and we're unlikely to get around to it in the near future. My apologies!
I'm running a k3s cluster with Raspberry Pis and can't use Bridge to Kubernetes, since the
routingmanager
doesn't support ARM architecture.Are there plans to support ARM in the future?