Cloudron Registry does not store images pushed via GitHub Actions (repository name not known)

[miednr]

Hi Cloudron team and everybody else,

I’m running into a persistent issue with the Cloudron Docker Registry and would appreciate your input.

Setup:
• Cloudron Registry app (DNS only, no Cloudflare proxy)
• Images are built and pushed via GitHub Actions using docker/login-action and docker/build-push-action
• Login to registry succeeds
• Push step completes successfully (no errors reported)

Observed behavior:
• After a successful push, the repository does not exist in the registry
• Registry API returns:
• /v2/ → 200
• /v2/<user>/<repo>/tags/list → NAME_UNKNOWN
• docker pull results in:
• repository name not known to registry
• manifest unknown

This happens regardless of:
• Image name (simple names tested, e.g. rag-gateway)
• Tags (latest, sha-…)
• Buildx settings (single platform, no provenance, no SBOM)
• Explicit registry host in login and tags

What was verified:
• Disk space is sufficient
• Auth is correct (App Password)
• Cloudflare is disabled for registry
• GitHub Actions runner cannot pull the image either after push
• Registry logs show no relevant errors during push or pull attempts

Conclusion so far:
It appears that the registry accepts the push but never persists the repository/manifest, making it impossible to pull afterwards.

Is this a known limitation or bug of the Cloudron Registry when images are pushed externally (e.g. via GitHub Actions / Buildx)?
Are there recommended settings or a supported workflow for external CI pushing images into the Cloudron Registry?

Thanks a lot for any guidance.

Best regards,
miednr

[james]

Hello @miednr
What user management did you chose for the Docker Registry app?

[miednr]

Hello @james
I used Cloudron for user management.

[james]

Hello @miednr
When you build a docker image localy and push it the same way witht he same credentials, does that work?

[miednr]

@james

Thanks for your attention to my two issues (with builder & registry). It's really much appreciated. But, I decided to use an external builder and an external registry and succeeded in implementing a custom app in Cloudron this way. I wanted to give you some feedback with the two threads and hoped for a quick solution. But I did move on and will stay on this route for this project. But maybe later, I will try Cloudron Builder and Cloudron Registry again. At the moment, I solved my problem with other tools. Thank you!

[timconsidine]

@miednr I build all my apps using local device docker, push to a cloudron private registry and use cloudron install --image xxx.
I feel guilty in some way for not using Cloudron Builder, but local gets the job done fine, so good that you got your build out and deployed.