# ARM64/aarch64 suppport (Debian Linux) for filebeat, metricbeat

**URL:** https://discuss.elastic.co/t/arm64-aarch64-suppport-debian-linux-for-filebeat-metricbeat/227419
**Category:** Beats
**Created:** [April 9, 2020, 11:27pm UTC](https://discuss.elastic.co/t/arm64-aarch64-suppport-debian-linux-for-filebeat-metricbeat/227419 "2020-04-09T23:27:54Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)
#### Post date: [April 10, 2020, 5:53pm UTC](https://discuss.elastic.co/t/arm64-aarch64-suppport-debian-linux-for-filebeat-metricbeat/227419/2 "2020-04-10T17:53:54Z")

</div>

Hey @siva-eh, welcome to discuss!

I wonder why both `helper_other.go` and `helper_aix.go` are being compiled, only one of them should be compiled, what version of go are you using?

In any case I would recommend you to build the packages on your workstation using beats scripts. They use docker with the same parameters and go versions as the distributed binaries.  
For example you can build Filebeat for arm64 using [mage](https://magefile.org/), running the following command from `x-pack/filebeat`:

```auto
PLATFORMS='+all linux/arm64' mage package

```

When this command finishes, you will find the packages in the `build/distributions` directory.

You can find more information about this topic in the following threads:

- [Build 7.0 for arm64 failed](https://discuss.elastic.co/t/build-7-0-for-arm64-failed/222033)
- [File/Packet/Metric beat on Raspi Centos 7 (armhf/armv7l)](https://discuss.elastic.co/t/file-packet-metric-beat-on-raspi-centos-7-armhf-armv7l/184048)

---

_[View the full topic](https://discuss.elastic.co/t/arm64-aarch64-suppport-debian-linux-for-filebeat-metricbeat/227419)._