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

Extend installation script to work for machines with ARM processor #86

Open
tommy1199 opened this issue Jun 29, 2022 · 4 comments
Open

Comments

@tommy1199
Copy link

tommy1199 commented Jun 29, 2022

Version

v0.0.12

Linux Version

5.15.0-39-generic

Is your feature request related to a problem? Please describe.

When following the Installation description, the latest version of bee is installed, but it always downloads the amd64 version of the binary (see here).

On an ARM64 machine the downloaded binary will not work.

Describe the solution you'd like

The installation script shall take the outcome of uname -m into account to decide what binary shall be downloaded.

Describe alternatives you've considered

No response

Additional Context

No response

@lgadban
Copy link
Collaborator

lgadban commented Jul 7, 2022

Unfortunately this is due to the fact that we currently do not support ARM.

We do have adding multi-arch builds on our roadmap, but until that gets implemented we should probably be more clear of our support (and maybe even fail the installation script if it detects non-AMD architecture)

@tommy1199
Copy link
Author

There is already an ARM binary of bee available e.g. here, so it looks like there is already a multi-arch build. Is there something missing for the ARM support?

@lgadban
Copy link
Collaborator

lgadban commented Jul 8, 2022

The real piece of functionality that's missing is we are building the probes specifically with the x86 headers.

So to truly support this, we need a way of flagging the underlying architecture at both build and run time. This shouldn't be too difficult to implement, we just haven't had a chance to dig into it yet.

@tommy1199
Copy link
Author

Thanks for the explanation. Would be great to see it on the roadmap in the future.

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