Cloudron App Install Update Error Bug

[DualOSWinWiz]

@joseph @girish

On one Cloudron instance, both new app installs and existing app updates fail with Docker registry / image pull errors.
Another Cloudron instance (similar setup) does not show this issue.

After investigation, the failures occur only when Docker registry credentials are saved in Cloudron settings. Rebooting the server had no effect. Removing the saved Docker registry credentials immediately fixes installs and updates.

This affects normal operations like routine app upgrades and fresh deployments.

⸻

Steps to reproduce
1. Go to Cloudron Settings → Docker Registries
2. Save Docker registry credentials (e.g., Docker Hub or private registry)
3. Attempt to:
• Install a new app or
• Update an existing app
4. Operation fails during image pull
5. Remove saved Docker registry credentials
6. Retry install/update → succeeds

⸻

Logs

App install / update failure (sanitized):

Error: pull access denied for <CLOUDRON_IMAGE>,
repository does not exist or may require authorization:
server message: insufficient_scope: authorization failed

Error response from daemon:
unauthorized: authentication required

Docker daemon log:

time="2025-01-02T11:24:08Z" level=error
msg="Handler for POST /v1.44/images/create returned error:
unauthorized: authentication required"

Cloudron apptask log:

TaskError: Error pulling image <CLOUDRON_IMAGE>:<TAG>
exit status 1
at ChildProcess.<anonymous> (/home/yellowtent/box/src/docker.js:312:23)

⸻

Troubleshooting Already Performed
• Server reboot
• Retried install/update multiple times
• Compared with another Cloudron instance (working)
• Removed Docker registry credentials → issue resolved immediately

⸻

System Details

Generate Diagnostics Data

Not generated yet. Can provide if requested.

⸻

Cloudron Version

9.0.15

⸻

Ubuntu Version

Distributor ID: Ubuntu
Description: Ubuntu 24.04.2 LTS
Release: 24.04
Codename: noble
Kernel: Linux 6.8.0-90-generic

⸻

Cloudron installation method
• ISO Image

⸻

Output of cloudron-support --troubleshoot

Vendor: Generic
Linux: 6.8.0-90-generic
Ubuntu: noble 24.04
[OK] docker is running
[OK] docker version is correct
[OK] nginx is running
[OK] dashboard cert is valid
[OK] dashboard is reachable
[OK] box v9.0.15 is running

⸻

Additional notes / hypothesis

This looks like a registry credential scoping or precedence issue, where user-saved Docker credentials are applied globally and interfere with Cloudron’s own image pulls, affecting both installs and updates.