-
The mysql-addon repo is at https://git.cloudron.io/cloudron/mysql-addon and according to that repo naming convention also the others.
The sftp addon is at https://git.cloudron.io/cloudron/docker-sftp (not sure why that repo name ended up like it is)
On a side topic, does anyone know of some good naming convention for docker images when it comes to supporting multi-arch?
For example:
cloudron/mysql-amd64:2.3.1(amd64)
cloudron/mysql-arm64:2.3.1(arm64) -
@nebulon said in Cloudron on a Raspberry pi?:
On a side topic, does anyone know of some good naming convention for docker images when it comes to supporting multi-arch?
I think the preferred way is to not have the architecture in the name or tag, but rather populate the manifest properly: https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/
-
-
@nebulon thanks! I was able to find most of them, but still missing graphite, turn and mail. Are those regular docker containers as well, and if so, are their dockerfiles published on git.cloudron? A search for those terms did not yield any meaningfule results for me.
On your side topic: I went looking for the arm64 version of the base ubuntu image, and it's published as multi-platform, so I guess there's no need to publish under another name, like @fbartels already answered. What I did have to do, though, was to strip the sha256 hash from the
FROMstatement. When I tried building on the rpi keeping the hash, docker selected the amd64 version of the image. Not sure how we'd go about making sure the image passes the integrity check (which I assume is why the has is there in the first place) while also being able to build for different architectures.@mehdi Man, I appreciate it! It was almost about a month just to get my hands on one, then weird networking stuff, trying to sneak in a few hours of banging on this problem in between work... Haha! A lot of fun though! So thanks for the kudos, they're highly appreciated, especially coming from you!
@girish yeah, I'm publishing to a private docker container (which I packaged together with verdaccio in a custom app just to have docker and npm private registers haha), so that part is good, I'm tagging them pointing to it and it's all good.
Haven't run the tests yet, though.
-
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/)
-
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 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 Are you using buildx? We bumped 5.6.2 to have docker 19 so we can have buildx
-
@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?
-
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!
-
@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 installandnpm test. -
To be clearer, like this (say with postgres addon). The tests will always test the latest
cloudron/{addonname}testimage.$ 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) -
@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.
-
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
authandadd databasetests pass, but I always get a timeout on theremove databasetest, 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?
-
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?
-
@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!
