Precompiled agent and nginx engine for ARM64 #2288
Labels
Comments
|
We would need an arm server added to our CI, but i'll keep this as an enhancement request. |
|
Could you include the arm packages from the next release process? We are migrating our Java based applications from AWS t3a to t4g Instances for better performance and cost reduction. Each application has its own Active Admin service which is deployed in the same instance. Since there is no precompiled binaries available for arm, we had to hold the migration and keep those services to be still in t3a Instances. |
|
If this is important to people, here's where you can submit a PR adding support for building arm binaries: https://github.com/phusion/passenger_binary_build_automation |
|
ok @CamJN, looks like one needs to
(probably this list will increase as far as one pushed the investigation). I estimate that this will take well at least one week of work, if one doesn't care about maintainability of the scripts...) |
|
Yes, holy build box is based on centos 6 because glibc is forwards compatible but not backwards compatible. So we need to use a base image that's got the oldest glibc that our prebuilt binaries will be used with. |
|
@CamJN have you already answered the question why don't you statically link your executable? |
|
@nilleb see this Q/A for why statically linking glibc is a bad idea: https://stackoverflow.com/questions/57476533/why-is-statically-linking-glibc-discouraged other libs are statically linked |
|
@CamJN so, would it be reasonable to use arm64v8/centos:8, given that you have no precompiled binaries consumers today? |
|
Seems like CentOS 7 might be a better choice since CentOS 8 is not long for this world: https://wiki.centos.org/About/Product |
|
Do you have any news? |
|
It would be nice to have on Raspberry Pi's, especially since they now all come with 64-bit OS, based on Debian 11 |
|
@FooBarWidget @CamJN any new here? because it looks like you just need to add ARM based machine into you autobuild stack |
|
I am using Raspberry Pi 4 and looking at this issue, it seems it is still not available? |
|
All you need is just to compile Passenger on Arm64 machine -- I did it and it works perfectly. Also if you wanna to use arm based docker images -- you need to modify way of installing passenger and nginx inside install script (install from source or precompiled debs) |
|
For now, I ended up using Puma, I will check later how to compile Passenger on an Arm64 machine. |
|
I ran into this today when trying to test our production environment automation using Docker on an M1 Mac. |
|
To build passenger for development in docker I'm using this script: version should match with your version from Gemfile |
|
Docker and APT both have arm64 packages now, RPM and prebuilt non-packaged binaries are still being worked on. |
|
I'm seeing the following trying to setup the docker image we build the precompiled passenger agent and nginx binaries in: That If anyone has the expertise to help with this it would be appreciated. I'm running out of time to add things to the upcoming 6.0.17 release, so precompiled arm binaries might need to slip to the next release. |
|
Ugh looks like the arm rpm packages are at risk now too (also because of qemu) due to this: https://gitlab.com/qemu-project/qemu/-/issues/1147 |
|
this has been done for a while now, forgot to close before |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Question 1: What is the problem?
ARM64 is an increasingly common platform these days, so I was surprised to find that there was no precompiled agent available. Could this be added? It takes quite a while to build both of these...
Question 2: Passenger version and integration mode:
Open source 6.0.5 standalone
Question 3: OS or Linux distro, platform (including version):
Ubuntu 20.04 ARM64
I think the rest of the questions are not applicable in this case.
The text was updated successfully, but these errors were encountered: