# Gosu binary in arm64 image

**URL:** <https://forums.percona.com/t/gosu-binary-in-arm64-image/38549>\
**Category:** Percona Distribution for PostgreSQL\
**Tags:** percona, bugs\
**Created:** [July 3, 2025, 4:31pm UTC](https://forums.percona.com/t/gosu-binary-in-arm64-image/38549 "2025-07-03T16:31:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![scheibling](https://avatars.discourse-cdn.com/v4/letter/s/3ec8ea/32.png) [@scheibling](https://forums.percona.com/u/scheibling)\
**Post date:** [July 3, 2025, 4:31pm UTC](https://forums.percona.com/t/gosu-binary-in-arm64-image/38549/1 "2025-07-03T16:31:23Z")

</div>

It looks like there are some issues with the container image builds (percona/percona-distribution-postgresql), where the AMD64 version of gosu is included in the ARM64 images leading to the container not starting up properly and showing an exec format error. I’ve had a look at a handful of 17.x/17.x-arm64 builds and all have the same issue from what I can see.

I’ve worked around it for now with a custom dockerfile that fetches the correct gosu version, but is this something you might be able to have a look at?

> **Dockerfile**
>
> ```auto
> FROM percona/percona-distribution-postgresql:17-arm64
> 
> ADD --chown=1001:1001 https://github.com/tianon/gosu/releases/download/1.17/gosu-arm64 /usr/bin/gosu
> 
> RUN chmod +x /usr/bin/gosu
> 
> ```

---

<div class="post-metadata">

**Author:** ![Evgeniy\_Patlan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/evgeniy_patlan/32/41_2.png) [@Evgeniy\_Patlan](https://forums.percona.com/u/Evgeniy_Patlan)\
**Post date:** [July 4, 2025, 10:45am UTC](https://forums.percona.com/t/gosu-binary-in-arm64-image/38549/2 "2025-07-04T10:45:35Z")

</div>

Hey @scheibling  
Thanks for your report. We have created a jira task to fix it.