Cloudron on a Raspberry pi?

[malvim]

Hey, guys.

So, this is what's going on currently:

I was able to build and run tests for, with minimal adaptations, the docker-base-image project, and the following addons:

• docker-sftp
• mongodb-addon
• mysql-addon
• redis-addon
• turn-addon

That leaves mail-addon, docker-graphite and postgresql-addon

Mail needs more setup as @girish said, so I'm not doing it for now. I was not able to clone the docker-graphite project, as I think I've mentioned before, so still waiting on what to do in this case.

In trying to understand a bit more of what's going on with the postgreql-addon tests hanging, I found it hangs in any test that uses connectClient, like the remove database and use database tests:

describe('remove database', function () {
    const data = { database: 'removetestdatabase', username: 'removetestuser', password: 'somepassword', locale: 'C' };

    before(function (done) {
        addDatabase(data, done);
    });

    it('succeeds', function (done) {
        request.delete(`https://${ip}:3000/databases/${data.database}?access_token=${CLOUDRON_POSTGRESQL_TOKEN}&username=${data.username}`, { rejectUnauthorized: false }, function (error, response, body) {
            expect(error).to.be(null);
            expect(response.statusCode).to.equal(200);

            connectClient(data, function (error) {
                expect(error).to.not.eql(null);
                client.end(done);
            });
        });
    });
});

In this case, addDatabase runs ok, and it makes sense since it is tested before.

The function is called, request.delete is called, the two expects pass, and then the function INSIDE connectClient (with the expect(error) line) never runs.

Can anyone else (besides @girish, who ran the tests and seen them run fine) run this and see what happens? This is happening on my laptop as well, not only on the Pi, but if I can't get this to go, I can't get the tests to pass on the pi, and we won't be able to trust everything runs okay.

[girish]

@malvim Are you testing this on a mac?

[malvim]

@girish Nope. Ubuntu 20.04 on both my laptop and a server, Ubuntu 18.04 on the raspberry pi. All with the same result.

[girish]

It works for me here atleast. I am guessing that you are unable to connect to the container IP maybe? Can you try installing psql tooling and connect via IP address? You can put a log in connectClient to see the credentials.

$ 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 (369ms)
      ✓ succeeds when added again
    remove database
      ✓ succeeds (125ms)
    use the database
      ✓ can create extension (82ms)
      ✓ can create table foo
      ✓ can insert into table foo
      ✓ can read from table foo
      ✓ restart (5091ms)
      ✓ can read from table foo
    backup and restore
      ✓ succeeds to create backup (443ms)
      ✓ succeeds to create new database (412ms)
      ✓ succeeds to clear new database (426ms)
      ✓ succeeds to restore backup (940ms)
      ✓ succeeds to check restore data
    restore of invalid dump fails
      ✓ succeeds to create backup (186ms)
      ✓ succeeds to clear new database (424ms)
      ✓ fails to restore backup (185ms)
    restore of existing dump
      ✓ succeeds (1721ms)


  21 passing (36s)

[malvim]

Hey,

So I commented out the remove database tests because I had trouble connecting from the container, but the next test, use the database, starts like this:

// psql -h localhost -U usetestuser  -d usetestdatabase
describe('use the database', function () {
    const data = { database: 'usetestdatabase', username: 'usetestuser', password: 'somepassword', locale: 'C' };

    before(function (done) {
        async.series([
            addDatabase.bind(null, data),
            connectClient.bind(null, data)
        ], done);
    });

So I ran "psql -h localhost -U usetestuser -d usetestdatabase", using 'somepassword' as a password, and was able to connect, both from inside the container and from my host machine.

connectClient still doesn't connect, and, I get this on the screen:

    auth
      ✓ fails without access_token
      ✓ fails with invalid access_token
      ✓ succeeds
    use the database
usetestuser somepassword usetestdatabase 172.18.0.2 5432
      1) "before all" hook

  3 passing (2m)
  1 failing

  1) Postgresql Addon
       use the database
         "before all" hook:
     Error: Timeout of 100000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/malvim/Projetos/Pi/docker/postgresql-addon/test/test.js)
      at listOnTimeout (internal/timers.js:551:17)
      at processTimers (internal/timers.js:494:7)

   
      2) "after all" hook

[malvim]

Also, it does not seem to be network-related, since I get the same behavior on an ubuntu 20.04 VPS I have...

[malvim]

I tried recreating the steps inside the container using node, and could connect. I'm really at a loss here right now...

[Lonkle]

@malvim Wish I had my Pi now so I could help test! Soon tho. ️

[malvim]

Hey, @Lonk! You mind testing this on your laptop? I'm not getting these errors only on the Pi, I'm getting them on my amd64 laptop and amd64 server as well!

Repo is here: https://git.cloudron.io/cloudron/postgresql-addon, it's just a matter of:

• cloning it;
• building the image locally (docker build -t cloudron/postgresqladdontest .)
• installing dependencies (npm install)
• running the test (npm test)

Could you run this somewhere and see if you have the same problem?

Thanks!

[malvim]

MAN, it seems I'm running into ALL KINDS of weird problems hahaha!

I started going into postgresql node client's code, and it seemed to be some weird behavior of EventEmitter, which was weird...

I installed nvm and tested with older node distributions, and it ran fine on my laptop! So it seems, @girish, that the test code for postgresql-addon does not run with node v14 or later on my machines. Tested with v12 and v13 and it was all fine. What version are you using for tests?

Moving on to the next hurdle, I guess hahah!

[girish]

@malvim said in Cloudron on a Raspberry pi?:

So it seems, @girish, that the test code for postgresql-addon does not run with node v14 or later on my machines

Aha! I feel like I have hit this issue before. Indeed, when we updated the box code to use node 14 lots of things fail (not sure why). We use node 10.18.1 everywhere. This is why the hotfix and code enforces it. For future reference, always use the node in scripts/createReleaseTarball in the box repo.

[malvim]

@girish okay, cool, I'll use that. It's good news, then, that the OTHER tests even ran!

So, for what it's worth, the code seemed to fail on the use of EventEmitter. A class was dispatching an event and the corresponding listener was not triggered, so if you ever need to investigate further, maybe that's a start.

[nebulon]

I have ordered a RaspberryPi 4 now as well and plan to use that as a home server, so hopefully we can get this supported well in the future Very curious to get my hands on what you have already managed to get working!

[robi]

There's the new keyboard that includes an rPi inside too.

[nebulon]

@malvim I've also got a Raspberry Pi 4 now. Can you give an update on where you are and do you have forked repos with arm changes somewhere?

[nebulon]

To give a short update from my side, with the information already posted here, I was able to get the box (the main Cloudron controller process) up and running on the Pi 4 as well as successfully install Cloudron as such. I have only just started on the base image and the other addons, so any patches here are welcome.

To collect the changes, I am creating arm64 branches in the relevant repos, for example https://git.cloudron.io/cloudron/box/-/commits/arm64 and https://git.cloudron.io/cloudron/docker-base-image/-/commits/arm64

On top of this, I am trying to implement a better provisioning workflow for development, this is similar to the hotfix, so it is still aimed towards developers porting stuff to arm. More info on this later.

[Lonkle]

@nebulon So quickly! Nice work.

I want to convert my app to run on ARM so I'll be getting the same board you got to verify the OpenVPN Client and all of its features are able to work in an ARM environment.

This is so cool, love ARM.

[nebulon]

Well it really remains to be seen how powerful such a board is to run common apps through docker

[Lonkle]

@nebulon True, but even if it could run 1. Not even that well, imagine a future with the Rasberry Pi 8. ARM CPUs are getting insane.

[mehdi]

@nebulon said in Cloudron on a Raspberry pi?:

Well it really remains to be seen how powerful such a board is to run common apps through docker

I'm running like 4 containers on my Raspberry pi at home, it's super smooth, and it's only a RPi 2 ! The RPi 4 is gonna be more than capable of running a few apps for home usage I think