Cloudron App limit without subscription too low
-
Situation:
While developing I would like to make use of the "Cloudron Build Service" (app #1) pushing to an also cloudron hosted Image Registry (app #2).Problem:
Trying to run the fresh built app now fails due to app limit (max. 2)Suggestion:
Do not count the "Cloudron Build Service" app on non-Premium instances.
(Image registry might be more difficult - cause there are various of them)P.S.
Would be also great to be able to runcloudron build
using a self signed certificate. -
Sounds like you need a subscription.
Here's my referral code link that I think will give a month for free https://cloudron.io/?refcode=5adcafc820c53c3d
Enjoy!
-
Also you don't need to the Cloudron build client. If you have docker on your local machine you can simply do a
docker build
instead.@Quhu assuming this is related to your vagrantfile. Just drop the build server and registry app. Instead manually run https://docs.docker.com/registry/.
-
Thanks for all the inputs.
Can someone please elborate the difference between:
docker build
andcloudron build
?My assumption was:
cloudron build
is doing much more. e.g. linting CloudronManifest, running integration tests (if any)....If there is no difference - there is no need to adapt the maximum of allowed apps.
-
you can cut out the part of the registry hosted on the same system if you use dockerhub
-
@Quhu said in Cloudron App limit without subscription too low:
Can someone please elborate the difference between:
docker build
andcloudron build
?It is explained in the docs at https://docs.cloudron.io/packaging/tutorial/
-
From the docs https://docs.cloudron.io/packaging/tutorial/ :
The build service app is installed on a separate Cloudron (not production Cloudron) and acts as a proxy for building docker images and also pushes them to your registry.
In other words: no difference.