It might not need any, since the production docker install instructions should be smart enough to automatically pull the most updated aarch64 build. But I don’t have a pi so I can’t fully test, but iav on GitHub helped set it up.
Hrm… I’ll have to do some searching. I hate having to do those aarch builds every time cause they’re really slow on my machine. Maybe we will have to move to some external deployer.
Or there might be a way to specify a use latest compatible version in the docker compose file.
Though it looks like we dont have any actual documentation on how to install the ARM version.
It might not need any, since the production docker install instructions should be smart enough to automatically pull the most updated aarch64 build. But I don’t have a pi so I can’t fully test, but iav on GitHub helped set it up.
I dont think so, the arm builds have a different tag. So it will just download the specified tag, and fail to run because its compiled for x86.
Hrm… I’ll have to do some searching. I hate having to do those aarch builds every time cause they’re really slow on my machine. Maybe we will have to move to some external deployer.
Or there might be a way to specify a use latest compatible version in the docker compose file.
We can setup a build server for release builds like I said.
No idea about the compose arch, I am not aware of anything like that (but i only use x86).
Basically check this out you’ll see this build has 2 OS/s or archs. Its called a multiarch docker manifest
Oh interesting.