Cloudron on a Raspberry pi?

[malvim]

Okay, so another question: Do we depend on mongodb being 4.0, or can we upgrade it to 4.2?

It seems mongodb 4.0 on arm64 only has support for ubuntu 16.04 (as per https://docs.mongodb.com/manual/administration/production-notes/)

[girish]

https://git.cloudron.io/cloudron/turn-addon is the turn addon and https://git.cloudron.io/cloudron/docker-graphite/ is graphite (the names are a bit here and there). The mail server is not open, I have sent you an invite though.

[malvim]

@girish Thanks, I'll check them out!

[girish]

@malvim said in Cloudron on a Raspberry pi?:

Okay, so another question: Do we depend on mongodb being 4.0, or can we upgrade it to 4.2?

yeah, we can bump it. But it requires the usual round of testing against all apps.

[malvim]

@girish Cool. I'll bump it to 4.2 (4.4 needs ubuntu 20.04) and keep pushing hehehe. I'll ping people here when I have something we can run tests on.

[girish]

@malvim Are you using buildx? We bumped 5.6.2 to have docker 19 so we can have buildx

[malvim]

@girish Not yet, I tried installing it for cross-platform building, but had some errors and didn't want to waste time, so I'm now just building the images from the pi itself. Later today I might have to start using it again for installing cloudron, so that might become enought of a hassle that I try again.

Anyone here with experience building for other architectures using buildx?

[malvim]

Hey, all.

Happy to say this is now going on on my raspberry pi:

I have NO idea wheter stuff is really working hahaha.
I'll probably choose a simple app and build it for arm64, then try to install it from command line and run tests, maybe?

Not sure how to run tests against addons, or even apps. Is there some documentation around about this? @girish, could you point me somewhere? Thanks!

[girish]

@malvim Wow, that's some incredible progress! If the status indicator is green, it's pretty sure that the addon containers are responding to health checks!

For the test for the addons, there is a test/ inside the repo of each addon. You can just do npm install and npm test.

[girish]

To be clearer, like this (say with postgres addon). The tests will always test the latest cloudron/{addonname}test image.

$ docker build -t cloudron/postgresqladdontest .
$ cd test
$ npm install # only have to do this once
$ npm test

> postgresql-addon@1.0.0 test /home/girish/yellowtent/postgresql-addon
> mocha --bail ./test/test.js



  Postgresql Addon
Error response from daemon: network with name cloudron already exists
    auth
      ✓ fails without access_token
      ✓ fails with invalid access_token
      ✓ succeeds
    add database
      ✓ succeeds (410ms)
      ✓ succeeds when added again
    remove database
      ✓ succeeds (140ms)
    use the database
      ✓ can create extension (49ms)
      ✓ can create table foo
      ✓ can insert into table foo
      ✓ can read from table foo
      ✓ restart (5241ms)
      ✓ can read from table foo
    backup and restore
      ✓ succeeds to create backup (392ms)
      ✓ succeeds to create new database (422ms)
      ✓ succeeds to clear new database (449ms)
      ✓ succeeds to restore backup (875ms)
      ✓ succeeds to check restore data (47ms)
    restore of invalid dump fails
      ✓ succeeds to create backup (175ms)
      ✓ succeeds to clear new database (434ms)
      ✓ fails to restore backup (174ms)
    restore of existing dump
      ✓ succeeds (1895ms)


  21 passing (35s)

[girish]

@malvim Our e2e tests use this app - https://git.cloudron.io/cloudron/test-app . You can just build it like any other app and deploy it on Cloudron.

[malvim]

Hey, @girish!

So I was trying to run the tests on the raspberry pi, had some failures, but they're also failing on my regular amd64 laptop with ubuntu, so I'm not sure what's going on.

I tried specifically the postgresql addon like you mentioned, with no changes, the auth and add database tests pass, but I always get a timeout on the remove database test, every time. Mail and sftp addon also fail at different points, so I'm not trusting the failed tests on the rpi.

I thought about trying to run the tests on my production cloudron server, but not sure I should.

Have you ever been through this?

[Lonkle]

I think ARM is the future so I'll be following this thread, love what I'm reading so far. Good stuff.

@malvim But if your test is failing on x86 and ARM, it probably isn't a CPU related issue IMO.

[malvim]

@Lonk Yup, those are my thoughts as well. The thing is, it seems the devs are able to run the tests themselves, so it seems there are no obvious problems anywhere heheh.

[malvim]

Okay, so I ran the tests on my production cloudron and they all passed. It seems they don't run on a regular machine previously to installing cloudron? Is that true? And SHOULD they? Maybe I'm testing it wrong heheh.

But it would be nice if we could just run the tests outside of any cloudron installation, so I could test the images themselves, separately, on arm64 before going with another full install.

What do you guys say?

[Lonkle]

@malvim said in Cloudron on a Raspberry pi?:

Okay, so I ran the tests on my production cloudron and they all passed. It seems they don't run on a regular machine previously to installing cloudron? Is that true? And SHOULD they? Maybe I'm testing it wrong heheh.

Your steps for testing it on local are different right? Since production is already running. What are your testing steps in each scenario?

But it would be nice if we could just run the tests outside of any cloudron installation, so I could test the images themselves, separately, on arm64 before going with another full install.

What do you guys say?

I'd say that's possible. We could just use Docker itself? That's what I do locally.

Anyway, what Rasberry Pi are you developing this on? I'll go run out and get one to see if I run into similar issues. ️ Very interested in Cloudron on ARM in 2030!

[malvim]

@Lonk said in Cloudron on a Raspberry pi?:

Your steps for testing it on local are different right? Since production is already running. What are your testing steps in each scenario?

Yeah, I'm doing what @girish outlined in his latest response in this thread: clone an addon repo, docker build the image tagging it with whatever name the test runner uses (cloudron/postgresqladdontest in this case), npm install and npm test.

It turns out I'm getting failures in all that I've tried so far, so I don't feel comfortable saying I "have successfully built the images" when I can't run the tests. But I can't run them on my laptop as well, so who knows? Haha!

Anyway, what Rasberry Pi are you developing this on? I'll go run out and get one to see if I run into similar issues. ️ Very interested in Cloudron on ARM in 2030!

I had never played with one till this year, they're fun! I got the latest model, the Raspberry Pi 4. Powerful little thing! It'd be great to have another pair of hands on this.

[girish]

@malvim We never run tests on the Cloudron itself, only on the laptop! Can you give the output of the npm test command? What is the error?

[Lonkle]

@malvim Well, consider yourself not alone in this endeavor! I'd love to help and am very interested in porting this to arm. Depends on the number of dependencies from the base image as well as Cloudron itself.

I'll post back here when I get my Raspberry Pi; I'm excited! ️

[malvim]

@girish said in Cloudron on a Raspberry pi?:

@malvim We never run tests on the Cloudron itself, only on the laptop! Can you give the output of the npm test command? What is the error?

malvim@zem:~/docker/postgresql-addon/test$ npm i
audited 152 packages in 2.419s
found 3 vulnerabilities (2 low, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details
malvim@zem:~/docker/postgresql-addon/test$ npm test

> postgresql-addon@1.0.0 test /home/malvim/docker/postgresql-addon
> mocha --bail ./test/test.js



  Postgresql Addon
Error: No such container: postgresql
    auth
      ✓ fails without access_token
      ✓ fails with invalid access_token
      ✓ succeeds
    add database
      ✓ succeeds (676ms)
      ✓ succeeds when added again (124ms)
    remove database
      1) succeeds

  5 passing (2m)
  1 failing

  1) Postgresql Addon
       remove database
         succeeds:
     Error: Timeout of 100000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/malvim/docker/postgresql-addon/test/test.js)
      at listOnTimeout (internal/timers.js:554:17)
      at processTimers (internal/timers.js:497:7)

Hey, @girish!

This is the output, and it just hangs after that and never exits. This happens on my laptop and on another machine I used for testing purposes. On my Cloudron, these tests passed and only the last one failed, the backup/restore one iirc.