Hi folks, Fleet 4.4.0 is now available :rocket: C...
# fleet
Hi folks, Fleet 4.4.0 is now available 🚀 Check out the changelog on GitHub, and as usual you can find binaries and containers on GitHub and Docker Hub respectively. 🍻 <!here>
🍻 3
🎉 11
@zwass hello, I am building fleet for arm64 successfully on ubuntu 20. Given that ARM based servers seem to be the future of the cloud with AWS Graviton, Ampere Altra CPUs currently being used by many as lower cost options, is there any reason in particular why you guys don't supply the built arm64 binary?
@Mystery Incorporated there's no reason in particular. Can you please file an issue detailing any steps you needed to take to make the build work -- we can work on adding this in future releases.
@zwass all I do is I follow the official steps for fleet to build it. I am not doing anything outside of your published instructions that's why I am so perplexed that arm binaries are not being built!
I did have to install python 2, I don't know if that is arm specific though I'd think probably not.
Copy code
make deps
make generate
^ This is all I do once pulling the code
Processor info:
Copy code
Architecture:                    aarch64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
CPU(s):                          2
On-line CPU(s) list:             0,1
Thread(s) per core:              1
Core(s) per socket:              2
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       ARM
Model:                           1
Model name:                      Neoverse-N1
Stepping:                        r3p1
BogoMIPS:                        50.00
NUMA node0 CPU(s):               0,1
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:        Mitigation; __user pointer sanitization
Vulnerability Spectre v2:        Not affected
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
We can hopefully configure goreleaser to add those binaries automatically. There's some CGO that complicates things but hopefully not too much.
@zwass if you require an arm VM to do it, oracle cloud gives free 4 core 24GB RAM server so you can utilise that to make binary for free if you need to do it on specific arm platform.
ty 1
@zwass thanks, the reason why I push for this idea is I fear the day that you guys use a new library or something that breaks the build for ARM. And so if you guys build for ARM, then you will detect issues like that. before release.
Yeah totally makes sense
👍 1
Checking if our regular release automation can cross-compile for ARM: https://github.com/fleetdm/fleet/runs/3822172228
@zwass bummer looks like it flopped.