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. App Packaging & Development
  3. Cloudron update didn't update

Cloudron update didn't update

Scheduled Pinned Locked Moved App Packaging & Development
7 Posts 3 Posters 1.0k 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 had an odd case just now with a custom python app.

    cloudron update
    

    ran successfully, but it did not update my application, the cold stayed the previous one. Reinstalling the app solved the problem.
    Here is what I did:

    • I used docker build with the no-cache option
    • I was definitely in the right folder
    • I pushed it to docker.io and confirmed in the dashboard that the push happened
    • I then used cloudron update to update the application

    The command ran successfully, but i could identify a typo in the code which I fixed locally but it wasn't fixed on the server. But it was after uninstalling and re-installing the app.

    Any ideas why that might be the case?

    1 Reply Last reply
    1
    • girishG girish moved this topic from Support on
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by
      #2

      Is it possible that you have the app twice installed and it updated another instance? The cloudron update command should give some indication on which instance it updated.

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

        Just to debug it , you can quickly check if cloudron status is showing the correct docker image after the cloudron update .

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

          Just to check, this is how I used cloudron update:
          cloudron update --app PATH --image docker.io/DETAILS (tag not specified)

          Since I specified the app path, how can it have updated another instance?

          When I run cloudron status after updating, it shows this: Could not determine app. Use --app to specify the app

          I just tried it again and didn't get any update either, but everything ran without any error message.

          girishG 1 Reply Last reply
          0
          • E ekevu123

            Just to check, this is how I used cloudron update:
            cloudron update --app PATH --image docker.io/DETAILS (tag not specified)

            Since I specified the app path, how can it have updated another instance?

            When I run cloudron status after updating, it shows this: Could not determine app. Use --app to specify the app

            I just tried it again and didn't get any update either, but everything ran without any error message.

            girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #5

            @ekevu123 cloudron status --app PATH

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

              Thank you. Yes, it shows the correct docker image.

              girishG 1 Reply Last reply
              0
              • E ekevu123

                Thank you. Yes, it shows the correct docker image.

                girishG Offline
                girishG Offline
                girish
                Staff
                wrote on last edited by
                #7

                @ekevu123 then, there is something wrong with the packaging. I am not sure how your Dockerfile looks like but maybe you copy over the code in a start up script or something ? Test the docker image locally using docker run -ti <docker_image> /bin/bash . Is it having the fixed code?

                1 Reply Last reply
                0
                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