# ARM Support

**URL:** https://meta.discourse.org/t/arm-support/353978
**Category:** Self-hosting
**Tags:** arm
**Created:** [February 23, 2025, 5:39pm UTC](https://meta.discourse.org/t/arm-support/353978 "2025-02-23T17:39:37Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [February 23, 2025, 6:40pm UTC](https://meta.discourse.org/t/arm-support/353978/6 "2025-02-23T18:40:02Z")

</div>

There’s also a difference, I think, in how ARM is pulled from the repo. I don’t fully understand:

> [@Launcher pulls an update on ‘enter app’](https://meta.discourse.org/t/launcher-pulls-an-update-on-enter-app/313051/3):
>
> … on Intel the script checks to see if a new image is available, but on ARM it will always pull. The reason given is that ARM always uses a fixed tag. For example, today, we see in the launcher script two possibilities:  
> `image="discourse/base:2.0.20240825-0027"`  
> or  
> `image="discourse/base:aarch64"`  
> and as you see, one of those is maintained carefully as new images are approved, and the other is left to the position of the tag.

---

_[View the full topic](https://meta.discourse.org/t/arm-support/353978)._
