# Support for ARM servers

**URL:** https://meta.discourse.org/t/support-for-arm-servers/36349
**Category:** Feature
**Tags:** arm
**Created:** [December 5, 2015, 12:29pm UTC](https://meta.discourse.org/t/support-for-arm-servers/36349 "2015-12-05T12:29:15Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![SentinelX101](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sentinelx101/32/44700_2.png) [@SentinelX101](https://meta.discourse.org/u/SentinelX101)
#### Post date: [December 5, 2015, 12:29pm UTC](https://meta.discourse.org/t/support-for-arm-servers/36349/1 "2015-12-05T12:29:15Z")

</div>

[https://github.com/discourse/discourse\_docker/issues/121](https://github.com/discourse/discourse_docker/issues/121)

Continuing on from the discussion on ARM support at GitHub.

ARM support would be extremely useful for owners of small communities like myself because of the extremely low price (like the [Scaleway 2GB ARM servers for €2.99](https://www.scaleway.com/pricing/)) and for those who can’t afford the move from cheap shared hosting to the dedicated or KVM machines that Discourse requires.

[https://community.scaleway.com/t/discourse-instantapp/452](https://community.scaleway.com/t/discourse-instantapp/452)

There has also been some discussion of this on the Scaleway forums, although much of this has been around getting Discourse working without using the Docker method.

---

<div class="post-metadata">

### Author: ![rriemann](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rriemann/32/115238_2.png) [@rriemann](https://meta.discourse.org/u/rriemann)
#### Post date: [January 13, 2016, 10:16am UTC](https://meta.discourse.org/t/support-for-arm-servers/36349/2 "2016-01-13T10:16:35Z")

</div>

> [@erlend\_sh](#):
>
> Users of Scaleway should encourage them to jump on the standard Discourse bandwagon. This is their blocker:

As @erlend_sh said, this is a blocker. No updates so far? Maybe Discourse could provide a list of non-ARM gems so far so that we could track here the process with respect to blocking dependencies?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [January 13, 2016, 11:21pm UTC](https://meta.discourse.org/t/support-for-arm-servers/36349/3 "2016-01-13T23:21:57Z")

</div>

Simplest thing to do is install Ruby on a scaleway copy our Gemfile and do a `bundle install`… what happens?

---

<div class="post-metadata">

### Author: ![rriemann](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rriemann/32/115238_2.png) [@rriemann](https://meta.discourse.org/u/rriemann)
#### Post date: [January 24, 2016, 5:51pm UTC](https://meta.discourse.org/t/support-for-arm-servers/36349/4 "2016-01-24T17:51:29Z")

</div>

`bundle install` is not an issue.

However, the _therubyracer_ and _v8_ gem requires some patches/different version. Otherwise, the  
`RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ENV=production bundle exec rake assets:precompile`  
does not finish, but break with a stack trace.

```plaintext
Purging temp files
abort:

==== JS stack trace =========================================

Security context: 0x3fd36f3d <JS Object>#0#
    1: /* anonymous */ [<eval>:~56513] (this=0x3fd36fe5 <JS Global Object>#1#,data=0x4f74cec5 <JS Array[2]>#2#)
    2: intersection [<eval>:57141] (this=0x4f74d431 <JS Object>#3#,argument=0x4f74ce7d <JS Object>#4#)
    3: /* anonymous */ [<eval>:58617] (this=0x4f70b199 <an Object>#5#,_dereq_=0x4f70b0f1 <JS Function>#6#,module=0x4f70b1a5 <an Object>#7#,exports=0x4f70b199 <an Object>#5#)
    4: arguments adaptor frame: 7->3
    5: s [<eval>:~2] (this=0x3fd36fe5 <JS Global Object>#1#,o=591,u=0x3fd08091 <undefined>)
    6: arguments adaptor frame: 1->2
    7: /* anonymous */ [<eval>:2] (this=0x3fd36fe5 <JS Global Object>#1#,e=591)

```

[stacktrace.txt](https://global.discourse-cdn.com/meta/original/3X/3/9/393e4d77c757b597047de0c3ac25a0187ba0a586.txt) (291 KB)

This seems to be the upstream bug: [TheRubyRacer 0.12.1 Segmentation Fault · Issue #317 · rubyjs/therubyracer · GitHub](https://github.com/cowboyd/therubyracer/issues/317)  
I posted recently a comment, but did not get a response.

Scaleway patches the Gemfile and Gemfile.lock in order to use local versions that have been downloaded from elsewhere: [https://github.com/scaleway-community/scaleway-discourse/blob/master/Dockerfile#L53](https://github.com/scaleway-community/scaleway-discourse/blob/master/Dockerfile#L53)

---

<div class="post-metadata">

### Author: ![balupton](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/balupton/32/255461_2.png) [@balupton](https://meta.discourse.org/u/balupton)
#### Post date: [June 30, 2016, 3:20pm UTC](https://meta.discourse.org/t/support-for-arm-servers/36349/5 "2016-06-30T15:20:14Z")

</div>

For those looking into this, a fair amount of progress has been made on this front:

[https://community.scaleway.com/](https://community.scaleway.com/)

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 30, 2016, 7:16pm UTC](https://meta.discourse.org/t/support-for-arm-servers/36349/6 "2016-06-30T19:16:47Z")

</div>

Nice looks like mini racer helped here @sam!

---

<div class="post-metadata">

### Author: ![ballerburg9005](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ballerburg9005/32/215193_2.png) [@ballerburg9005](https://meta.discourse.org/u/ballerburg9005)
#### Post date: [March 31, 2021, 3:49am UTC](https://meta.discourse.org/t/support-for-arm-servers/36349/7 "2021-03-31T03:49:08Z")

</div>

Is it working on ARM now?

Is it just a matter of messing with the install scripts, or are there really x86 binary blobs used?

Everyone has 100Mbit lines now, a lot of people have gigabit fiber internet at home. You can get a Cortex-A55 TV Box for $30, plug in your old SSD drive via USB 3.0 with a $3 adapter, install Linux and you are ready to go. It consumes virtually no power. The processing speed and disk speed is incredible. Often the ping is lower than in a datacenter. This is not even the future of hosting. It has been around for quite some time. It is totally superior to any mid-range server. There literally are only advantages.

---

<div class="post-metadata">

### Author: ![anon82467725](https://avatars.discourse-cdn.com/v4/letter/a/edb3f5/32.png) [@anon82467725](https://meta.discourse.org/u/anon82467725)
#### Post date: [April 1, 2021, 2:09pm UTC](https://meta.discourse.org/t/support-for-arm-servers/36349/8 "2021-04-01T14:09:13Z")

</div>

> [@ballerburg9005](#):
>
> Everyone has 100Mbit lines now, a lot of people have gigabit fiber internet at home.

Not everybody is fortunate enough to have access to that kind of internet speed (let alone fiber optic internet). Some people even have dial-up still. That is beginning to change in the United States, but not in regions of poverty. I guess it would be worth mentioning [Starlink](https://www.starlink.com/) though.

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [April 1, 2021, 2:27pm UTC](https://meta.discourse.org/t/support-for-arm-servers/36349/9 "2021-04-01T14:27:18Z")

</div>

You make a great point, but I think it’s even _more_ important in the datacentre.

Broad adoption of ARM in the datacentre could realise some huge energy efficiencies ([\> 2x ?](https://www.datacenterknowledge.com/hardware/huge-week-arm-data-center-too)) and lower costs which could have massive impact. This is a really responsible goal.

btw, this was recently discussed in this Topic: [Require ARM64 Support - #3 by david](https://meta.discourse.org/t/require-arm64-support/182171/3) suggesting that several dependencies (gem binaries) are not available outside of x86

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [December 7, 2021, 2:08pm UTC](https://meta.discourse.org/t/support-for-arm-servers/36349/10 "2021-12-07T14:08:10Z")

</div>

This is now supported

> **[Discourse on a Raspberry Pi](https://blog.discourse.org/2021/12/2021-12-07-discourse-on-a-raspberry-pi/)**
>
> Running a production instance of Discourse in a $35 Raspberry Pi 4

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [December 8, 2021, 1:33am UTC](https://meta.discourse.org/t/support-for-arm-servers/36349/11 "2021-12-08T01:33:26Z")

</div>