-
Notifications
You must be signed in to change notification settings - Fork 30
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
Wrong binaries in arm64 version of the docker images for nebula-operator #308
Comments
@svok Thanks a lot. I've fixed the issue, please try again. |
Thank you @MegaByte875. I confirm, installation's done |
Unfortunately, I've found few more images with wrong platform. The next image is just not strating. Presumably, it has similar problem. |
@svok Ok, I will fixed them asap. |
The next iteration and one more step futher. |
Since 1.7.0 vesoft/nebula-stats-exporter is not required anymore. Both nebula-operator and nebula-cluster have been installed successfully. Thank you. |
Describe the bug (required)
Docker image for linux/arm64 platform of the vesoft/nebula-operator:v1.6.3 at Docker Hub contains x86_64 (AMD64) binaries.
Your Environments (required)
Linux op1 5.10.110-rockchip-rk3588 #1.0.2 SMP Thu Apr 13 16:55:55 CST 2023 aarch64 aarch64 aarch64 GNU/Linux
How To Reproduce(required)
I'm trying to run nebula-operator on the ARM64 Kubernetes platform.
As I start
I get in the logs the following errors for both
nebula-operator-controller-manager-deployment
andnebula-operator-scheduler-deployment
:That's all. It is not working.
I pulled image
vesoft/nebula-operator:v1.6.3
(8cb85d69068e) and checked its content. This is the description of the /bin/sh file:The
controller-manager
file is also specified asAdvanced Micro Devices X86-64
.Expected behavior
The container for platform arm64 must contain correct ARM64 binaries rather then AMD64
The text was updated successfully, but these errors were encountered: