Cloudron Forum

If the image still isn't found, the Docker daemon fetches the image from the canonical repository on Docker Hub. that's a feature of docker daemon itself. Fallback through the list of configured registry-mirrors. The key here is that docker pull docker.io/cloudron/base is treated exactly as "docker pull cloudron/base" (implicit hub.docker.com) whereas docker pull registry.docker.com/cloudron/base is ignoring registry-mirror list because it is an explicit registry image ref. quay.io would also fail in a "restricted" network environment. One of the other solutions I considered is to allow a "cloudron base registry" option in the installer.

Hello @gomesm @gomesm said: Upgrading to 24.04.4 fixed the issue. Good to read! So another confirmed fix by upgrading Ubuntu.

@james said in Private docker registry in Cloudron: Hello @dualoswinwiz I have just created a personal access token with the Read-only permission. Configured Cloudron: [image: 1766752382547-8248133a-0064-4fa0-a724-828faf826879-image.png] and was able to install my custom app from a private repo. Did you use registry.hub.docker.com as the Server address? Nope i was using docker.io once i changed to registry.hub.docker.com its working thank you.