For those that are reading this post... If you plan to host the docker image yourself, this is critical to update the JSON of Docker Registry app with your Cloudron registry domain and credentials.

@nebulon Maybe that would be a great idea to add to the documentation that if a user wants to host the image himself, he should use his Cloudron docker registry domain instead of docker.io. The documentation is currently confusing ^^

Thanks again for your assistance.

Ah yeah, that's what I thought. Moved the build app to somewhere else. Would be nice to add --cpu-quota to the build command to mirror the apps settings (from https://dev.to/code42cate/dont-build-docker-apps-without-this-flag-48kg)

Right having unreliable and slow internet connection was one of the main reasons for us to create that buildservice app.

For the repository URLs, this is more like a docker quirk. The build service just passes those strings forward to docker.

@girish works perfectly fine now, thanks for the quick fix

@murgero yes, it should be safe to deploy within existing apps.

Just tried it and a cloudron build --set-build-service mybuild.service.com --build-service-token <token-from-/app/data/tokendb.json> --set-repository <your.docker.registry>/<appname> --tag latest now starts the build and pushes it to the repo. Thanks a thousand times, @girish. This is awesome.