Integrate a private docker registry

[adrw]

I'm in strong agreement with @robi and @msbt, I'm working on a custom app and using Cloudron as a stripped down much cheaper alternative to AWS for hosting and a private docker registry is the last missing puzzle piece since I don't want to publish the image in a public Docker registry. A Cloudron private docker registry would be greatly appreciated and I'd be happy to pitch in with testing from a Github Actions CI use case or local publishing.

[plusone-nick]

+1 on this for me too. Using Wappler to build no-code/low-code nodejs apps and need a private repo, ideally within cloudron

[ekevu123]

I just came across the same issue. I would like to push my images to the Private Docker Registry app which is on Cloudron as well - and it would be totally in-brand to allow both apps to interact with each other.

I tried changing the link in the config file according to the docs, but the standard is still set to docker.io.

[msbt]

Are you using the build-app? If so, did you adjust the config.json with your registry? You can also try cloudron build --set-repository and enter your private registry

[ekevu123]

I did adjust the config, but in the end, the tool just used docker.io/MY_LINK. If I use cloudron build without the build service, won't this build the image locally, but then push it into mr repository?

[nebulon]

Yes the build service is only optional in case a local docker setup is not viable or the upload speed is low. But otherwise by default it would build it locally and then push to the configured repository.

[ekevu123]

I lost track of this thread. Can I just confirm the original question? It seems like the build service works only with docker.io.

I tried changing it in docker.json, but all it does is that it adds my repository address to docker.io/library, which fails. I also tried cloudron build --set-repository, but that leads to the same result.

[nebulon]

does the image repository you set with --set-repository also contain the domain of your target registry? I think docker defaults to docker.io if not provided.

[ekevu123]

I got it. So, apparently, this works for me when I set the --set-repository using this structure: mydocker.registry.com/my-repo. It probably works then as well if I put the repo into the build service config, but then I could only push to one repo.
So, the solution seems to be to always manually specify the repository as well. Also, I copy-pasted my docker registry link, because it is quite long, and adding https:// at the beginning causes problems, but it works without it.

But at least I have a working way of handling this now, thank you! That is very helpful as I don't always have fast internet.

[nebulon]

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.