Cloudron on a Raspberry pi?

[Lonkle]

@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?

[nebulon]

@lonk for the core box code, essentially only two things were needed. The branch is at https://git.cloudron.io/cloudron/box/-/commits/arm64/

[iamthefij]

@nebulon said in Cloudron on a Raspberry pi?:

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 docker buildx though.

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.

[nebulon]

@iamthefij nice thanks for the pointers, when we got started on this this will help. I tried to use docker buildx but 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]

@nebulon careful with compiling on rPi's as they can overheat and burn out Having a small heatsink or fan handy helps a lot.

[nebulon]

@robi yup, I have a case for it with cooling

[yusf]

@nebulon You have that case that is the heatsink? It’s very nice.

[malvim]

@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...

[nebulon]

@yusf yes exactly that, makes it feel like a strong brick you could throw around

[iamthefij]

@nebulon would all binaries not run (eg. /bin/sh from within the base) or just Go binaries that you compiled within the buildx pipeline? 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 GOARCH variable via a build-arg would solve it.

Note: I personally have not used buildx yet, 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.

I think buildx is 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.

[MOrochena]

I was wondering what the current state of this is, as I would be extremely interested in migrating my Cloudron setup to a Raspberry pi.

[girish]

The project has stalled a bit unfortunately So far, there's not much interest in ARM server (apart from hosting on pi), I was hoping we will see more ARM servers mainstream...

[malvim]

Hey! I was working on this, but stumbled upon two issues:

1. As @girish said, there's not much interest in ARM servers, so it would be very low priority to integrate having different architectures into cloudron main code; and

2. I wanted to do this so I could host my cloudron at home, but since mos ISPs where I live won't let you expose port 80, 443, 25, etc., I lost interest in pursuing this.

If cloudron would support having nginx on custom ports, that would be cool for people wanting to host at home and with the same problem, but I think this is also not a priority now, as not too many people seem to be interested in this.

It's not too hard to make cloudron's install script work on a raspberry pi, though, but you'd have to maintain a fork, which was also not my interest at the time. If you want to, though, DM me and I can give you a few pointers.

[robi]

@malvim There's a nice thread on all the different tools you can use to expose apps under dev or home run services:
https://forum.cloudron.io/topic/6231/ngrok-alternatives-awesome-tunneling

Even if you don't have a domain, any subdomain provider will work, and I'm sure many of the forum members could offer a container that does just that on one of their subdomains if you don't already have one and a VPS.

[malvim]

@robi hey, thanks for the reply!

I'll take a look.

I currently do own a domain and run cloudron on a rented server, but I'm from Brazil and stuff is pretty bad here right now, and it's starting to be a bit too expensive for my purposes.

I thought about hosting at home, but stumbled upon this problem. I'll take a look ad that thread and see what I can use. Thanks again!

[robi]

@malvim said in Cloudron on a Raspberry pi?:

I currently do own a domain and run cloudron on a rented server, but I'm from Brazil and stuff is pretty bad here right now

We also have a thread on that.. search for "cheap vps" ..
my profile has a link to the affordable VPS servers I use.

[potemkin_ai]

@girish @nebulon , just wanted to add my voice to ARM (RPi) support.

More and more hostings appears with RPi with a very attractive pricing (8Gb RAM, 4CPU Cores * 2Ghz, 30Gb network HDD) for ~$15/month.

It would be also very handy for a private in-office use, for a more private use cases.

[lukas]

I'm also interested to run Cloudron on ARM based hardware

[Dennis4720 0]

Me too. Hetzner offers VPS' for less costs with ARM chips and so may other hosting providers these days. (=

[girish]

We are in the course of automating the build and testing of package updates. Once that is done, we can think about creating additional packages. Creating ARM builds for apps will automatically double our package count!