Cloudron on a Raspberry pi?
Lonk last edited by
@nebulon Well, that sounds to me like like not much work needs to be done, I'll do some PoC stuff myself and see the difficulty of converting the app. Docker is supposed to support multi arch so it's a matter of getting all the developer's to support multi arch upstream. So, I'll start submitting tickets for those things. Thanks for telling me where you were at, do you have your POC up anywhere yet?
@lonk for the core box code, essentially only two things were needed. The branch is at https://git.cloudron.io/cloudron/box/-/commits/arm64/
To give one simple example, any app using the go language, where we take the release builds, has to get some logic or separate Dockerfile to deal with arm.
I have some experience with this and have set up my own multi-arch go build pipelines using a single Dockerfile for some of my other apps: minitor-go, dockron, tag-checker, and for Python ones too: original minitor.
Here's a sample repo demonstrating my process: multiarch-pipeline-test. It's easier these days if your server has
Also, since with Cloudron we're most often building things that exist upstream, here's an example multi-arch build repo I have for the Golang project cadvisor. It will auto build a particular cadvisor version on a git tag so I just need to create a release on my Gitea server and the build is started and deployed. With cadvisor, I have to clone the whole repo and cross-compile the cadvisor binary for arm becaue there is no pre-compiled binary. If there is, it should be even easier to just pull that binary.
Anyway, I'm happy to help if there are any applications that may be critical to be ported.
@iamthefij nice thanks for the pointers, when we got started on this this will help. I tried to use
docker buildxbut I couldn't get it to work and produce binaries which would actually run on the raspberrypi, so I ended up using the raspberrypi to build the images itself, which surprisingly showed how beefy that board has become
robi last edited by
@nebulon careful with compiling on rPi's as they can overheat and burn out Having a small heatsink or fan handy helps a lot.
@robi yup, I have a case for it with cooling
yusf last edited by
@nebulon You have that case that is the heatsink? It’s very nice.
@nebulon yup! I tried it as well, and could not get it to work. building on the pi itself proved to be
the easiest way...
@yusf yes exactly that, makes it feel like a strong brick you could throw around
@nebulon would all binaries not run (eg.
/bin/shfrom within the base) or just Go binaries that you compiled within the
buildxpipeline? If it's the former, it may not be using the right base image. If it's the latter and the former works, perhaps setting the
GOARCHvariable via a build-arg would solve it.
Note: I personally have not used
buildxyet, but from what I can see it's a simpler, automatic version of what I'm trying to do with qemu that handles the manifest for you. So I think you should just be able to build without the muckiness of all the build-args I pass, but if not you can play with mixing those in until it works.
buildxis supported on my laptop, so I can give it a try, but it's not supported on my CI box yet, so I haven't switched.