Closed 93imagine closed 6 months ago
carrodher
commented
9 months ago There are some applications not supported in ARM due to different technical limitations. At this moment, we have an ongoing internal task to review those apps looking for a solution.
We'll update this ticket with more information when possible. In the meantime, we'll add the on hold label so it is not automatically closed by the stale bot.
MarcusElevait
commented
6 months ago Any news here? We're using the bitnami/mongodb image on our local development setups. Some of us are using a mac with an arm cpu and we have an ugly workaround to make this run, but would be better if you would provide image for multiple platforms.
carrodher
commented
6 months ago Any news here? We're using the bitnami/mongodb image on our local development setups. Some of us are using a mac with an arm cpu and we have an ugly workaround to make this run, but would be better if you would provide image for multiple platforms.
In the case of MongoDB, the upstream project does not provide ARM binaries so there is nothing to do on our side. See https://github.com/bitnami/charts/issues/3635
carrodher
commented
6 months ago In the case of Supabase, which was the original topic discussed in this issue, we're glad to share that all the related containers are now multi-arch, see
Name and Version
[bitnami/supabase] 2.7.0
What architecture are you using?
None
What steps will reproduce the bug?
1) Deploy helm on ARM 2) Default images pulled are amd64 3) There are no ARM build packages in the source: example: https://hub.docker.com/r/bitnami/supabase-storage/tags
Are you using any custom parameters or values?
No response
What is the expected behavior?
Pull ARM images on ARM systems.
What do you see instead?
There are no ARM images build. example: https://hub.docker.com/r/bitnami/supabase-storage/tags This causes the deploy to not work.
Additional information
Since Bitnami's charts seem to always support ARM I am surprised to see that there are not even ARM images build for this deployment. This makes me assume this is a bug.