Cloudron update - using wrong tag should not attempt the update
-
I have just used accidentally the wrong tag name for my cloudron update command, a non-existing one. However, I'd say this would ideally lead to a simple error message "Docker image not found" or similar. Instead it tried to update my app and crashed it in the process with the error message "Manifest not found", which is misleading, because the point is that the image itself doesn't exist.
-
mm, I can't really reproduce this. I get:
$ cloudron update --image some-random-image --app test => Waiting for app to be updated => Queued => Backup - Uploading app snapshot test.smartserver.io => Downloading image Error: Installation failed: Unable to pull image some-random-image. message: (HTTP code 404) unexpected - pull access denied for some-random-image, repository does not exist or may require 'docker login': denied: requested access to the resource is denied statusCode: 404 at waitForFinishInstallation (/home/girish/yellowtent/cloudron-cli/src/actions.js:287:64) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Command.update (/home/girish/yellowtent/cloudron-cli/src/actions.js:824:9) App update error: Installation failed: Unable to pull image some-random-image. message: (HTTP code 404) unexpected - pull access denied for some-random-image, repository does not exist or may require 'docker login': denied: requested access to the resource is denied statusCode: 404
Which is a reasonable error message I think.
-
Try using a non-existing tag in an existing repository to reproduce this. I get this:
cloudron update --app myapp.com --image my-existing-repository:randomtag
=> Waiting for app to be updated
=> Queued
=> Backup - Uploading app snapshot app
=> Backup - Copying postgresqldump .App update error: Installation failed: Unable to pull image XXX. message: (HTTP code 404) unexpected - manifest for XXX not found: manifest unknown: manifest unknown statusCode: 404