Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Feature Requests
  3. Cloudron update - using wrong tag should not attempt the update

Cloudron update - using wrong tag should not attempt the update

Scheduled Pinned Locked Moved Feature Requests
4 Posts 3 Posters 526 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • E Offline
    E Offline
    ekevu123
    wrote on last edited by
    #1

    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.

    1 Reply Last reply
    0
    • girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #2

      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.

      image.png

      1 Reply Last reply
      0
      • E Offline
        E Offline
        ekevu123
        wrote on last edited by
        #3

        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

        J 1 Reply Last reply
        0
        • E ekevu123

          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

          J Offline
          J Offline
          joseph
          Staff
          wrote on last edited by
          #4

          @ekevu123 the manifest error here refers to the docker image manifest. That part of the error message is from your upstream docker registry and not generated by cloudron.

          1 Reply Last reply
          1
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Bookmarks
          • Search