multi architecture support #802

vielmetti · 2017-04-03T20:03:54Z

It would be great if Mastodon could run on systems other than Intel, such as Raspberry Pi, ARMv8, etc. This would get it into the hands of people with home single-board computers running their own services, plus some new data center ARM servers.

The fastest path that I can think of to doing this is to build the system with an alternative docker-compose.yml file, and have it pick up the containers appropriate to each of those other systems (e.g. armhf, aarch64).

Some dependencies to track:

Raspberry Pi

Ruby: https://hub.docker.com/r/armhf/ruby/
Redis: https://hub.docker.com/r/armhf/redis/
Postgres: https://hub.docker.com/r/armhf/postgres/

ARMv8

Ruby https://hub.docker.com/r/aarch64/ruby/
Redis: https://hub.docker.com/r/aarch64/redis/
Postgres: https://hub.docker.com/r/aarch64/postgres/

An additional dependency is the Dockerfile itself, for that the probably best thing to do is to make a Dockerfile.{armhf,aarch64} with the proper changes.

vielmetti · 2017-04-03T21:22:02Z

Making progress, I hope to have a file or two in my fork to look at as WIP. There are an awful lot of dependencies in the gem file and the npm repo but nearly all of them work without incident on ARMv8.

hyc · 2017-04-04T00:10:51Z

Haven't decided yet if this is a job for an embedded DB like LMDB, or for a network service like OpenLDAP. postgres is clearly too much of a pig for the workload though, and redis can't do anything significant to improve the situation. Caching is relatively useless when you're under an onslaught of new content. Leaning towards OpenLDAP, which would allow clustering a bunch of servers off a single set of accounts.

vielmetti · 2017-04-04T01:10:45Z

The referenced issue knu/ruby-unf_ext#15 notes that the unf_ext gem fails to build in its rubygems version on ARM processors, but does build from source on github due to a few extra patches applied since the gem was updated.

Three ways forward:

fix upstream by releasing a new version of the gem with the fix included
work around in Dockerfile.{armhf,aarch64} by installing from source, not from the gem
update the Gemfile with gem 'uef_ext', git: 'https://github.com/knu/ruby-unf_ext.git'

vielmetti · 2017-04-04T02:05:52Z

The referenced issue npm/uid-number#3 reflects an issue where the Dockerfile builds as root, which the recent versions of npm object to.

One way forward that I found was adding npm config set unsafe-perm true to the Dockerfile.

vielmetti · 2017-04-04T17:26:42Z

Upstream is working on the ruby unf_ext gem.

vielmetti · 2017-04-04T21:04:53Z

The version of Ruby easily installable from apk on ARM from Alpine (2.3.3) is different from the Ruby 2.3.1 referenced in the Gemfile.

ghost · 2017-04-06T12:57:32Z

Keep up the good work, it might help to run mastodon on an internet cube (Olimex Lime 2).

vielmetti · 2017-04-06T21:56:55Z

https://www.armbian.com/olimex-lime-2/

DoubleMalt · 2017-04-17T14:58:49Z

I tried building the mastodon Docker image on a RPi3 today.

I first built a ruby:2.4.1 image according to the dockerfile described in the docker library manifest.
The docker fileI used was from https://github.com/docker-library/ruby.git, commit e98bec810e6f1bd88ad0106f2e3b3f3291f5f5bb, directory 2.4/alpine where I just prefixed alpine in the from line with armhf.

Then I used this as the base image for my mastodon build.
As there aren't many prebuilt binaries for ARM in the NPM repository I had to add python to the BUILD_DEPS.

Then it went through the bundling and was tripped up when yarn tried to build node-sass.

The error output was

error /mastodon/node_modules/node-sass: Command failed.
Exit code: 1
Command: sh
Arguments: -c node scripts/build.js
Directory: /mastodon/node_modules/node-sass
Output:
Building: /usr/bin/node /mastodon/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ '/usr/bin/node',
gyp verb cli   '/mastodon/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library=' ]
gyp info using node-gyp@3.4.0
gyp info using node@6.10.1 | linux | arm
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp ERR! UNCAUGHT EXCEPTION 
gyp ERR! stack TypeError: Cannot read property 'length' of undefined
gyp ERR! stack     at parse (/mastodon/node_modules/semver/semver.js:239:14)
gyp ERR! stack     at Function.valid (/mastodon/node_modules/semver/semver.js:255:11)
gyp ERR! stack     at processRelease (/mastodon/node_modules/node-gyp/lib/process-release.js:16:25)
gyp ERR! stack     at configure (/mastodon/node_modules/node-gyp/lib/configure.js:35:17)
gyp ERR! stack     at Object.self.commands.(anonymous function) [as configure] (/mastodon/node_modules/node-gyp/lib/node-gyp.js:66:37)
gyp ERR! stack     at run (/mastodon/node_modules/node-gyp/bin/node-gyp.js:72:30)
gyp ERR! stack     at _combinedTickCallback (internal/process/next_tick.js:73:7)
gyp ERR! stack     at process._tickCallback (internal/process/next_tick.js:104:9)
gyp ERR! System Linux 4.4.50-v7+
gyp ERR! command "/usr/bin/node" "/mastodon/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /mastodon/node_modules/node-sass
gyp ERR! node -v v6.10.1
gyp ERR! node-gyp -v v3.4.0
gyp ERR! This is a bug in `node-gyp`.
gyp ERR! Try to update node-gyp and file an Issue if it does not help:
gyp ERR!     <https://github.com/nodejs/node-gyp/issues>
Build failed with error code: 7

Tying to work from there.

vielmetti · 2017-04-17T15:09:42Z

@DoubleMalt - you are running armhf on your Pi 3? I ask because there are distros that support arm64

DoubleMalt · 2017-04-17T15:19:01Z

@vielmetti
Sent you an email to take this OT discussion elsewhere :)

marcust · 2017-04-17T15:31:50Z

@DoubleMalt I ran into the same thing when building on arm64 and did nodejs/node-gyp#1174

Still not sure what it means, but at least that fixed the build issue.

DoubleMalt · 2017-04-17T15:34:26Z

Actually if I first do npm install node-gyp (which pulls in 3.6.0), the yarn runs fine. I think the problem is that for some reason node-gyp 3.4 gets installed by yarn itself if it is not present.

DoubleMalt · 2017-04-18T06:25:55Z

Found a way to minimally invasive build the Docker container on ARM(hf). Will verify if this also works on aarch64.

I had to do yarn upgrade node-sass node-gyp to make yarn upgrade the yarn.lock file. A slight draback of that is that node-gyp shows up in the package.json.

If there are some yarn whisperers here, maybe they could tell me how to only upgrade the node-gyp (which is exclusively used by node-sass).

Will submit a pull request today as a basis for further discussion.

Merge upstream changes

SuperSandro2000 · 2019-05-25T01:55:41Z

I don't build my arm images on real hardware cause I don't have a reasonable arm server. I always use the cross compile feature from balenlib https://github.com/SuperSandro2000/docker-images/blob/master/reddiscord/arm32v7.Dockerfile#L1 .

J0WI · 2019-11-10T21:59:15Z

See also #9967

killua99 · 2020-05-11T18:37:01Z

I'm building for amd64 and arm/v7 (soon arm64 too) I'm using hardware to build then since I got tired of these long compilations libraries. You could check it at:

https://hub.docker.com/r/killua99/mastodon (alpine base adding buster-slim soon)
https://github.com/killua99/mastodon-docker

PureTryOut · 2020-07-02T11:36:34Z

Huh, just found this issue, so I guess the Docker image isn't supported on aarch64 yet, even if I build it myself? I did try to build the image myself and although it completes successfully, running it fails and reports standard_init_linux.go:211: exec user process caused "exec format error".

According to the Dockerfile ubuntu:20.04 is used as base image and I can run just that perfectly fine. However even running something simple as bash (docker run --rm -it mastodon bash) fails in the Mastodon container, but runs fine on the standard Ubuntu one. I have no clue at all what can cause this.

The Dockerfile itself suggests that arm64 should work fine, at least for the NodeJS part, and everything else seems to be compiled from source or installed from package managers which I assume do account for different architectures.

SuperSandro2000 · 2020-07-02T14:41:27Z

The tini in the image is x86. This PR should solve this.

xmflsct · 2020-10-20T20:38:51Z

The tini in the image is x86. This PR should solve this.

When can this be merged? I had the same issue on v3.2.1, and using your suggestion fixed the issue.

SuperSandro2000 · 2020-10-21T09:59:37Z

When can this be merged?

I solved the merge conflict which I somehow missed. So, now from my side.

killua99 · 2020-10-22T00:16:49Z

Someone has tried to compile Mastodon the last 4 month ? (even to the latest release is just 2 days old)

There is a common issue with bcrypt use on:

https://github.com/tootsuite/mastodon/blame/v3.2.1/Gemfile.lock#L177

connected with:

https://github.com/heartcombo/devise/blob/v4.7.2/Gemfile.lock#L87

bcrypt-ruby/bcrypt-ruby#201

Solution is to use the devise 4.7.3, so make a new tag on mastodon to bump this

Bobby99as · 2021-08-14T06:29:51Z

Anything new on this? It would be nice to see this working on arm

PureTryOut · 2021-08-14T08:16:46Z

It already works on arm. I'm currently running it on a RockPro64 with postmarketOS installed, that's aarch64 (arm64).

nightpool · 2021-08-14T14:19:52Z

I'm going to close this issue since it seems like ARM support is mostly working, in the future please open individual issues for arm compatibility problems!

xmflsct · 2021-08-15T11:31:24Z

I now run Mastodon on ARM, see guide here https://github.com/xmflsct/oracle-arm-mastodon.

swaldie added the enhancement label Apr 3, 2017

vielmetti mentioned this issue Apr 4, 2017

0.0.7.2 fails to build on arm with gcc6 (i.e. C++14) knu/ruby-unf_ext#15

Closed

vielmetti mentioned this issue Apr 4, 2017

Error: could not get uid/gid npm/uid-number#3

Closed

vielmetti mentioned this issue Apr 8, 2017

portability: unf_ext gem version available that works on ARM #1250

Closed

1 task

Pym mentioned this issue Apr 13, 2017

docker-compose build fails #1644

Closed

1 task

DoubleMalt mentioned this issue Apr 18, 2017

Make Docker image buildable on ARM #2065

Merged

Gargron added suggestion Feature suggestion and removed enhancement labels Oct 20, 2018

hannahwhy pushed a commit to hannahwhy/mastodon that referenced this issue Oct 30, 2018

Merge pull request mastodon#802 from ThibG/glitch-soc/merge-upstream

08c0f8b

Merge upstream changes

SaraSmiseth mentioned this issue Feb 9, 2020

Docker build fails with "ELF: not found" #13055

Closed

nightpool closed this as completed Aug 14, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

multi architecture support #802

multi architecture support #802

vielmetti commented Apr 3, 2017 •

edited

vielmetti commented Apr 3, 2017

hyc commented Apr 4, 2017

vielmetti commented Apr 4, 2017 •

edited

vielmetti commented Apr 4, 2017

vielmetti commented Apr 4, 2017

vielmetti commented Apr 4, 2017

ghost commented Apr 6, 2017

vielmetti commented Apr 6, 2017

DoubleMalt commented Apr 17, 2017

vielmetti commented Apr 17, 2017

DoubleMalt commented Apr 17, 2017

marcust commented Apr 17, 2017

DoubleMalt commented Apr 17, 2017

DoubleMalt commented Apr 18, 2017

SuperSandro2000 commented May 25, 2019

J0WI commented Nov 10, 2019

killua99 commented May 11, 2020

PureTryOut commented Jul 2, 2020

SuperSandro2000 commented Jul 2, 2020

xmflsct commented Oct 20, 2020

SuperSandro2000 commented Oct 21, 2020 •

edited

killua99 commented Oct 22, 2020

Bobby99as commented Aug 14, 2021 •

edited

PureTryOut commented Aug 14, 2021 •

edited

nightpool commented Aug 14, 2021

xmflsct commented Aug 15, 2021

multi architecture support #802

multi architecture support #802

Comments

vielmetti commented Apr 3, 2017 • edited

Raspberry Pi

ARMv8

vielmetti commented Apr 3, 2017

hyc commented Apr 4, 2017

vielmetti commented Apr 4, 2017 • edited

vielmetti commented Apr 4, 2017

vielmetti commented Apr 4, 2017

vielmetti commented Apr 4, 2017

ghost commented Apr 6, 2017

vielmetti commented Apr 6, 2017

DoubleMalt commented Apr 17, 2017

vielmetti commented Apr 17, 2017

DoubleMalt commented Apr 17, 2017

marcust commented Apr 17, 2017

DoubleMalt commented Apr 17, 2017

DoubleMalt commented Apr 18, 2017

SuperSandro2000 commented May 25, 2019

J0WI commented Nov 10, 2019

killua99 commented May 11, 2020

PureTryOut commented Jul 2, 2020

SuperSandro2000 commented Jul 2, 2020

xmflsct commented Oct 20, 2020

SuperSandro2000 commented Oct 21, 2020 • edited

killua99 commented Oct 22, 2020

Bobby99as commented Aug 14, 2021 • edited

PureTryOut commented Aug 14, 2021 • edited

nightpool commented Aug 14, 2021

xmflsct commented Aug 15, 2021

vielmetti commented Apr 3, 2017 •

edited

vielmetti commented Apr 4, 2017 •

edited

SuperSandro2000 commented Oct 21, 2020 •

edited

Bobby99as commented Aug 14, 2021 •

edited

PureTryOut commented Aug 14, 2021 •

edited