-
Notifications
You must be signed in to change notification settings - Fork 103
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
Make launcher available per-architecture #1149
Comments
Looks right. Order seems about right too. I agree we don't care about the old notary stuff. |
I learned today that we have employees using Raspberry Pi (arm64) devices for software development, but are unable to use Kolide for compliance monitoring on them so I am very much interested in this issue. Customer support pointed me in the direction of this issue. Thanks! |
Hi @tstromberg! We've started digging into windows arm64 support and have a beta for that. We haven't done nearly as much for linux arm64 support. Which distros are people using? How do you imagine the installation working? I'm somewhat concerned that the number of possible downloads becomes unmanageable as it grows. |
It'd be great to be able to use this on Ubuntu on ARM! |
XAM customer here - we're just starting to prototype Ubuntu 24.10's very early support for Snapdragon X Elite processors. Maybe Fedora would be the other option for us, but for supportability, we wouldn't be looking at anything more esoteric. |
this issue is opened since a year, what's going on ? It's not like arm is some architecture that just came up recently , the whole apple ecosystem use it and we don't necessarely run macOS on mac @RebeccaMahany |
We will likely want to start supporting launcher on ARM for Windows and Linux, and potentially may want to ship separate builds per-architecture for macOS instead of shipping a universal build.
This encompasses:
<binary>/<os>/<arch>/<channel>/release.json
: [TUF autoupdater] Include arch in release file path and download file path #1195 (waiting on next osquery release)I think it's likely not worthwhile to update the old TUF server and old autoupdate code to account for this.
The text was updated successfully, but these errors were encountered: