# Installing and hosting taiga on ARM64 based machine

**URL:** <https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622>\
**Category:** Self hosted Taiga\
**Created:** [January 21, 2023, 12:07am UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622 "2023-01-21T00:07:10Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![m3tr0n](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@m3tr0n](https://community.taiga.io/u/m3tr0n)\
**Post date:** [January 21, 2023, 12:07am UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/1 "2023-01-21T00:07:10Z")

</div>

Hello everyone. I have been trying to figure out how to install taiga on an ARM64 based server but unfortunately I couldn’t accomplish that via docker. Is there a way to do it ? Any help will be appreciated. Thanks!

---

<div class="post-metadata">

**Author:** ![david.barragan](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/david.barragan/32/293_2.png) [@david.barragan](https://community.taiga.io/u/david.barragan)\
**Post date:** [January 23, 2023, 11:18am UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/2 "2023-01-23T11:18:32Z")

</div>

Hi @m3tr0n,

We don’t have the docker images compiled to be able to deploy them on this architecture yet. However, we know that Taiga works perfectly on ARM64 because it is the architecture we use for our SaaS. You can follow the [installation guide to setup Taiga from source code](https://docs.taiga.io/setup-production.html#setup-prod-from-source-code).

Of course it will be something that we will keep in mind for our future major versions.

---

<div class="post-metadata">

**Author:** ![m3tr0n](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@m3tr0n](https://community.taiga.io/u/m3tr0n)\
**Post date:** [January 23, 2023, 1:32pm UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/3 "2023-01-23T13:32:57Z")

</div>

@david.barragan Thank you for the confirmation David. I did try to install it directly from the source code but ran into some problems but now that I know that it is possible, I’m sure a bit of troubleshooting will be all I need to do.

Also yes, a docker image for the ARM64 compatible version will be very helpful. Thank you.

---

<div class="post-metadata">

**Author:** ![m3tr0n](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@m3tr0n](https://community.taiga.io/u/m3tr0n)\
**Post date:** [January 25, 2023, 2:51am UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/4 "2023-01-25T02:51:40Z")

</div>

![Screenshot from 2023-01-25 08-19-13](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/1X/9cd453e84659a44934f986e669315090df7a27e8.png)

@david.barragan Am I supposed to replace rabbitmquser and rabbitmqpassword in

```auto
sudo rabbitmqctl add_user rabbitmquser rabbitmqpassword

```

If yes then maybe the installation guide could use an editing check.

---

<div class="post-metadata">

**Author:** ![david.barragan](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/david.barragan/32/293_2.png) [@david.barragan](https://community.taiga.io/u/david.barragan)\
**Post date:** [January 25, 2023, 8:12am UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/5 "2023-01-25T08:12:36Z")

</div>

Yes, you can use whatever values ​​you want. But remember that you will have to modify them in the rest of the settings files so that taiga-back and taiga-events can connect with RabbitMQ.

---

<div class="post-metadata">

**Author:** ![m3tr0n](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@m3tr0n](https://community.taiga.io/u/m3tr0n)\
**Post date:** [January 25, 2023, 1:50pm UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/6 "2023-01-25T13:50:39Z")

</div>

Finally everything connects and functions except that now I get a 403 error when I try to load up the webpage

---

<div class="post-metadata">

**Author:** ![david.barragan](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/david.barragan/32/293_2.png) [@david.barragan](https://community.taiga.io/u/david.barragan)\
**Post date:** [January 26, 2023, 8:54am UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/7 "2023-01-26T08:54:09Z")

</div>

Ummm, maybe some mistake in the nginx settings

---

<div class="post-metadata">

**Author:** ![m3tr0n](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@m3tr0n](https://community.taiga.io/u/m3tr0n)\
**Post date:** [January 26, 2023, 10:43am UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/8 "2023-01-26T10:43:25Z")

</div>

There was an error in the initial configuration provided in the guide. I made it work though so thanks and maybe check the guide for errors if someone in your team has the time for it. Thanks!

---

<div class="post-metadata">

**Author:** ![J\_E\_C\_B](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/j_e_c_b/32/976_2.png) [@J\_E\_C\_B](https://community.taiga.io/u/J_E_C_B)\
**Post date:** [April 28, 2023, 4:38pm UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/9 "2023-04-28T16:38:02Z")

</div>

Any news about this topic?

---

<div class="post-metadata">

**Author:** ![KoaRaiden](https://avatars.discourse-cdn.com/v4/letter/k/bb73d2/32.png) [@KoaRaiden](https://community.taiga.io/u/KoaRaiden)\
**Post date:** [July 5, 2023, 2:32pm UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/10 "2023-07-05T14:32:48Z")

</div>

I’ve been facing some difficulties while attempting to install Taiga on [a](https://dailysportsupdates.com/webcric-live-streaming/)n ARM64 based server using Docker. Unfortunately, I haven’t been able to successfully complete the installation through this method. I’m reaching out to the community to seek guidance and assistance. If anyone has experience or knowledge regarding installing Taiga on an ARM64 architecture or knows an alternative approach that could work, your help would be greatly appreciated. Thank you in advance for any suggestions or advice you can provide.

---

<div class="post-metadata">

**Author:** ![david.barragan](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/david.barragan/32/293_2.png) [@david.barragan](https://community.taiga.io/u/david.barragan)\
**Post date:** [July 5, 2023, 5:04pm UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/11 "2023-07-05T17:04:01Z")

</div>

What is the error? Knowing it makes our task easier.

---

<div class="post-metadata">

**Author:** ![david.barragan](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/david.barragan/32/293_2.png) [@david.barragan](https://community.taiga.io/u/david.barragan)\
**Post date:** [July 5, 2023, 5:10pm UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/12 "2023-07-05T17:10:07Z")

</div>

Our SaaS at [https://tree.taiga.io](https://tree.taiga.io) works on an ARM infrastructure (amazon). You can follow this guide and install it from source code [Install Taiga in Production](https://docs.taiga.io/setup-production.html#setup-prod-from-source-code)

---

<div class="post-metadata">

**Author:** ![gergiskhan](https://avatars.discourse-cdn.com/v4/letter/g/46a35a/32.png) [@gergiskhan](https://community.taiga.io/u/gergiskhan)\
**Post date:** [December 8, 2023, 6:09pm UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/13 "2023-12-08T18:09:42Z")

</div>

I am presently trying to get this to work on a Raspberry Pi 4, running DietPi, a Debian variant.

I installed the docker images according to the setup guide. First issue - the images are amd64, not arm64. however, there is a way using QEMU to apparently run the images.

My new problem is that the gunicorn workers are timing out constantly.

```auto

taiga-docker-taiga-back-1 | [2023-12-08 17:58:56 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:74)
taiga-docker-taiga-back-1 | [2023-12-08 17:58:56 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:76)
taiga-docker-taiga-back-1 | [2023-12-08 17:58:56 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:78)
taiga-docker-taiga-back-1 | [2023-12-08 17:58:57 +0000] [1] [WARNING] Worker with pid 76 was terminated due to signal 9
taiga-docker-taiga-back-1 | [2023-12-08 17:58:57 +0000] [1] [WARNING] Worker with pid 78 was terminated due to signal 9
taiga-docker-taiga-back-1 | [2023-12-08 17:58:57 +0000] [1] [WARNING] Worker with pid 74 was terminated due to signal 9
taiga-docker-taiga-back-1 | [2023-12-08 17:58:57 +0000] [80] [INFO] Booting worker with pid: 80
taiga-docker-taiga-back-1 | [2023-12-08 17:58:57 +0000] [82] [INFO] Booting worker with pid: 82
taiga-docker-taiga-back-1 | [2023-12-08 17:58:57 +0000] [84] [INFO] Booting worker with pid: 84

```

I suspect this might be due to possible emulation. Unfortunately, I am not skilled enough in Docker to attempt to rebuild the containers, nor was I able to build Taiga from scratch on this same machine. I’m unable to get it to work using the full source installation. I assume I’d have to do this to get a docker container that is arm64 native?

Can anyone help figure out this worker error? I am so close to being able to deploy this fully.

Alternatively, can someone please build the latest images for arm64? The best I could find were years old.

---

<div class="post-metadata">

**Author:** ![AarKiMos](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/aarkimos/32/1902_2.png) [@AarKiMos](https://community.taiga.io/u/AarKiMos)\
**Post date:** [December 15, 2023, 11:03am UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/14 "2023-12-15T11:03:01Z")

</div>

Hi, I was also trying to install taiga on a ARM64 instance (oracle cloud - ubuntu). After going through installing from source guide, I was stuck with a 404 on frontend and 403s on static files returned by nginx. (Admin was running fine otherwise).

This error was due to nginx user `www-data` not being able to read files from `taiga` user’s home directories.

The default config starts like this and sets `www-data` as nginx user

`/etc/nginx/nginx.conf`

```auto
user www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;
.
.
.

```

Adding `www-data` user to `tiaga` user’s group solved it for me. Not sure if this is the best way to do.  
I hope this helps.

---

<div class="post-metadata">

**Author:** ![stevenlafl](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/stevenlafl/32/2579_2.png) [@stevenlafl](https://community.taiga.io/u/stevenlafl)\
**Post date:** [May 22, 2024, 5:17am UTC](https://community.taiga.io/t/installing-and-hosting-taiga-on-arm64-based-machine/622/15 "2024-05-22T05:17:29Z")

</div>

This will build ARM64 images.

```auto
#/bin/bash
REGISTRY="YOUR_REGISTRY"
CURRENT_VERSION="6.8.0"
IMAGES=("front" "back" "events" "protected")

for image in "${IMAGES[@]}"; do
  git -C "taiga-$image" pull || git clone -b stable https://github.com/taigaio/taiga-$image
  docker buildx build --platform=arm64 -t $REGISTRY/taiga-$image:$CURRENT_VERSION -f taiga-$image/docker/Dockerfile taiga-$image/
  docker push $REGISTRY/taiga-$image:$CURRENT_VERSION
done

```

It takes a long time, so if you don’t want to wait, image tags:  
stevenlafl/taiga-front:6.8.0  
stevenlafl/taiga-back:6.8.0  
stevenlafl/taiga-events:6.8.0  
stevenlafl/taiga-protected:6.8.0