Cloudron on a Raspberry pi?
@malvim Yeah man, PM me what you want on it, and I'll reimage it soonest and beam over creds.
@malvim Yeah, you can adjust that apt line as needed. Essentially, you have to make the https://git.cloudron.io/cloudron/box/-/blob/master/baseimage/initializeBaseUbuntuImage.sh script succeed. You can make the script standalone, it does not require any args.
nginx ARM packages - http://nginx.org/packages/ubuntu/pool/nginx/n/nginx/
Node ARM packages - https://nodejs.org/dist/v10.18.1/
Docker ARM packages - https://download.docker.com/linux/ubuntu/dists/bionic/pool/stable/
Also, I saw you are testing in Focal. One issue I hit (even on x86) was that collectd has issues with the python3 plugin. I haven't gotten around to fix that.
@girish Yeah, I'll try bionic again, it just crashed on something related to
initramfs-tools, and focal still does when i try to install
linux-generic, which I assume has something to do with kernel images and the like? This stuff is a bit above my current knowledge, so I'm not exactly sure what I'm doing heheh.
@malvim Cloudron doesn't really use any of the packages like linux-kernel, initramfs etc directly. I think it's just added there for completeness. Feel free to remove them.
@girish great! I was already commenting out these lines to see where it went.
So it seems I'm losing name resolution after installing
unbound. Installation of
resolvconfis not a problem, but as soon as I install unbound, lots of names stop resolving and I can't install anything anymore.
Not sure how unbound works, might have to go into it a bit more, but my guess is maybe the problem is inside my provider. I'll check with @will later to see if we can try it in his device, and see if the problem persists.
Just to keep you guys updated on what's going on: I commented out unbound just to go through (and probably have to come back to it later, but still).
I also switched to installing nginx from the repos instead of downloading a specific package with curl manually, as their version is
arm64and it seems the rpi I'm on is
armhf, which I know nothing about but some nginx-arm64 dependencies were not being met.
I switched node to the
armv7lpackage and it went ok.
I switched docker packages to
armhf, they intalled okay, but it seems I don't have the overlay kernel module loaded and have NO IDEA how to load it heheh. A few google searches still got me kinda stuck, I'll try again tomorrow.
Alright, so I learned how to load kernel modules, and the problem now is that the
/partition in this particular provider is over nfs, and overlay is not supported.
So, as this is not a problem with cloudron on a rasberry pi, and is particular to this provider, I'm thinking of trying to change the docker driver tomorrow, just to see how far I can get to...
So my Raspberry Pi finally arrived, and I could start testing cloudron on it without the hassles I was having with the hosting company. So here are some thoughts and the current bump on the road I'm trying to overcome:
- I was able to install cloudron pretty easily with just a few changes to the
cloudron-setupscript itself, and to
installer.shinside the cloudron package that is downloaded from the internet by
- The changes in
cloudron-setupwere just not upgrading the kernel (not installing
linux-generic, like I talked to @girish about earlier in this thread), and not downloading the cloudron package from the website, instead using my modified version so I coud change things and test.
- The changes inside the package were pretty much just changing
arm64in all the downloaded packages
- Another important change is the boot part, where cloudron changes grub files, and I had to switch things to the
- I was able to keep
unbounduntouched, I guess it was a problem with the hosting company
So that was what I had to do, and here are the things I'm currently thinking about this:
- It would be good to have the current architecture in a variable, say
arch, but there's a few questions to answer, like:
- The rpi I was using in the hosting company was not
armhf, I think. If there's different architectures for different models, we'd have to test it on others. I currently own an arm64 rpi 4 model B.
- Some downloaded packages use
amd64in their names, and stuff like
armv7lfor armhf architecture, it seems. We'd have to map these package names to their architectures in a more explicit way, I think.
- The rpi I was using in the hosting company was not
- We'd have to extract the boot configuration (grub vs /boot/firmware confs) somewhere
I'm now facing ANOTHER problem, which is: it seems my ISP doesn't allow me to forward low ports like 80 and 443, so I can't really host cloudron from inside my home at the moment. I'm starting another thread asking for ideas with that, but I can't test cloudron apart from the installation process (which went smoothly all the way to the domain setup, but then I can't access it because of port forwarding restrictions).
So there it is, this is were I'm at currently regarding installing cloudron on an rpi, I'd greatly appreciate any input, thoughts, ideas, whatever you guys have.
- I was able to install cloudron pretty easily with just a few changes to the
That's fantastic news I replied here about the port forwarding - https://forum.cloudron.io/topic/3324/testing-from-home-without-nat-port-forwarding-capability
yusf last edited by
Stellar effort getting this far, @malvim! It’s sounds quite promising.
robi last edited by
@malvim arm64 is only available on the rPi 4 as far as I recall.
armhf is for the previous models as they are 32bit ARM chips.
It would be cool if both were supported and autodetected, but you should be aware of the arch differences between the different models.
@robi Yeah, I don't know much about the different architectures, and at present I don't have access to any earlier armhf model, so I'll keep pushing with what I have for now. Maybe if we can suport the arm64 rPi 4 to start, some modifications (like explicitly handling architecture information, different boot locations and whatnot) will help us deliver cloudron to other models more easily.
Just keeping everything relating to the rpi setup in this thread:
So I finished setting up, went to https://<ip> like
cloudron-setupsays, and started domain setup. As per the other thread, I set up my IP to the interface I'm using (
wlan0). I'm using Amazon AWS as a domain provider, and set up the keys and such.
So cloudron was able to create the DNS records (using a subdomain, like
pi.mydomain.com, which should - and does - create an A record
my.pi.mydomain.compointing to my
Afterwards, though, cloudron is never able to check for the records, as I cannot seem to resolve the
my.pidomain from inside the pi.
Other stuff that happens:
sudo: unable to resolve host ubuntu, even though it does change user to root no problem;
ubuntuis the default hostname on a bare ubuntu 18.04 install on the pi;
- I can
digother domains that are already hosted on my zone, and get corret responses.
dig- ing for the
my.pidomain either times out with a "no server could be reached" message, or, when I do it RIGHT AFTER a successful
digto other domain, returns an "empty" response (with a line indicating 0 answers, like this:
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1)
I'm a bit over my skill level on this, so if anyone could chime in, id'd be greatly appreciated. Either with an idea on what might be going on, or maybe something I could do/check/run to get mor info on what might be going on.
sudo: unable to resolve host ubuntu
This is expected and has nothing to do with arm. To get over that you have to setup the hostname correctly. In your case the hostname is still set to the default
ubuntuwhereas following your example it has to be
@nebulon huh, that makes sense, but I thought this was supposed to be done by cloudron during setup? I don’t remember having to manually set the hostname in any other cloudron setup before, but I might just have forgotten...
It looks like the blocking issue is the DNS does not work? Does
host my.pi.mydomain.com 127.0.0.1work on the pi?
jamesgallagher last edited by
If there's nothing private in it; could you post your /etc/hosts file?
Yup, so I'm testing it again from scratch.
@jamesgallagher, here's the entire contents of my
/etc/hostsright after running
cloudron-setup, but before setting up the domain in the browser:
127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts
@girish, the record is already there with the previous IP, and right now I'm just after
cloudron-setup, but before
setupdns.htmlon the browser. I've ran a bunch of commands, here are the results:
host my.pi.<mydomain.com>- not found
host my.pi.<mydomain.com> 127.0.0.1- not found
host www.google.com 127.0.0.1- ok (huh, unbound seems to be somewhat working)
host code.<mydomain.com> 127.0.0.1(gitea instance on production cloudron) - OK!
host my.<mydomain.com> 127.0.0.1(production cloudron admin) - NOT FOUND! (wat?)
And I ran
host my.pi.<mydomain.com>on my local machine, outside the pi, and it works and returns the old record (
192.168.0.109from my previous attempt).
I'm now setting up DNS in the browser, just to check what happens, I'll re-run the commands and post here.
This post is deleted!
Okay, so some weird stuff seems to be going on with the DNS lookup thing, I think. Here's what happened after running cloudron domain setup (
setupdns.htmlon the browser):
I ran it pointing to a subdomain of my domain (
pi.<mydomain.com>), and pinted it to a network interface (
wlan0, in this pi's case), as @girish suggested. So I'm tailing
/home/yellowtent/platformdata/logs/box.log, and here's what I see:
2020-10-07T23:43:30.489Z box:dns/waitfordns waitForDns (try 20): my.pi.<mydomain.com> to be 192.168.0.6 in zone <mydomain.com> 2020-10-07T23:43:30.497Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has A record at 18.104.22.168 2020-10-07T23:43:30.498Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has A record at 22.214.171.124 2020-10-07T23:43:30.500Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has A record at 126.96.36.199 2020-10-07T23:43:30.501Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has A record at 188.8.131.52 2020-10-07T23:43:35.499Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has CNAME record at 184.108.40.206 2020-10-07T23:43:35.501Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has CNAME record at 220.127.116.11 2020-10-07T23:43:35.503Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has CNAME record at 18.104.22.168 2020-10-07T23:43:35.504Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has CNAME record at 22.214.171.124 2020-10-07T23:43:35.516Z box:dns/waitfordns isChangeSynced: NS ns-1094.awsdns-08.org (126.96.36.199) errored when resolve my.pi.<mydomain.com> (A): Error: queryCname ENODATA my.pi.<mydomain.com> 2020-10-07T23:43:35.516Z box:dns/waitfordns waitForDns: my.pi.<mydomain.com> not done ns: ["ns-1094.awsdns-08.org","ns-1877.awsdns-42.co.uk","ns-234.awsdns-29.com","ns-907.awsdns-49.net"] 2020-10-07T23:43:35.525Z box:dns/waitfordns isChangeSynced: NS ns-1877.awsdns-42.co.uk (188.8.131.52) errored when resolve my.pi.<mydomain.com> (A): Error: queryCname ENODATA my.pi.<mydomain.com> 2020-10-07T23:43:35.629Z box:dns/waitfordns isChangeSynced: NS ns-234.awsdns-29.com (184.108.40.206) errored when resolve my.pi.<mydomain.com> (A): Error: queryCname ENODATA my.pi.<mydomain.com> 2020-10-07T23:43:35.635Z box:dns/waitfordns isChangeSynced: NS ns-907.awsdns-49.net (220.127.116.11) errored when resolve my.pi.<mydomain.com> (A): Error: queryCname ENODATA my.pi.<mydomain.com>
So I go to my LOCAL machine to check the records:
$ host my.pi.<mydomain.com> my.pi.<mydomain.com> has address 192.168.0.6 $ host my.pi.<mydomain.com> ns-1094.awsdns-08.org Using domain server: Name: ns-1094.awsdns-08.org Address: 2600:9000:5304:4600::1#53 Aliases: my.pi.<mydomain.com> has address 192.168.0.6 $ host ns-1094.awsdns-08.org ns-1094.awsdns-08.org has address 18.104.22.168 ns-1094.awsdns-08.org has IPv6 address 2600:9000:5304:4600::1 $ host my.pi.<mydomain.com> 22.214.171.124 ;; connection timed out; no servers could be reached
So it seems when I look up the records using Amazon's DNS server IP's instead of their names, I can't look them up! EVEN ON MY LOCAL MACHINE! I have no idea what might be going on. Then, going back to the pi:
$ host my.pi.<mydomain.com> ns-1094.awsdns-08.org Using domain server: Name: ns-1094.awsdns-08.org Address: 2600:9000:5304:4600::1#53 Aliases: my.pi.<mydomain.com> has address 192.168.0.6 $ host my.pi.<mydomain.com> 126.96.36.199 ;; connection timed out; no servers could be reached $ host my.pi.<mydomain.com> 127.0.0.1 ;; connection timed out; no servers could be reached $ host my.pi.<mydomain.com> localhost ;; connection timed out; no servers could be reached
So... Yeah, this is where I'm at right now. Totally at a loss hahah! NO IDEA what might possibly be going on now...