Replies: 4 comments 2 replies
-
I updated Komodo manually. |
Beta Was this translation helpful? Give feedback.
-
How? Thanks |
Beta Was this translation helpful? Give feedback.
-
I logged in to the Komodo LXC and changed to the /opt/komodo directory. Stopped the current Komodo container, removed the current image, then used this docker compose command to pull the new image and bring up the container (this assumes you're using the mongo compose file)
There might be an easier way, but this worked for me. |
Beta Was this translation helpful? Give feedback.
-
I had the same problem, and the following terminal command forces a new docker pull if there's a new Komodo release, and should always work (if you used a Helper script to originally install it):
So, I had this exact discussion with the maintainers of the helper scripts on Discord (pointing out that the Komodo docker images on Github were updated, so why doesn't the update script work?) and their answer was:
I'm not knowledgeable enough to fight them on it, but I do think it highlights I problem I often run into with those scripts: you're completely reliant on the way the script dev wrote it. Even if updates are available, if they aren't in alignment completely with the way the project releases files, then you're stuck unless you do it yourself. I could go down the list of other Helper script projects I've installed, only to later rip them out and install docker manually with my own compose files directly from the source project. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is anyone familiar with the Proxmox Helper Script to install Komodo in an LXC? Initial install was fine, working great, I see that 1.18.4 is out and the Helper Script says it's at 1.18.4:

...but when I run "update" in the LXC, I still have 1.18.3 installed. It looks like the "update" completes successfully, but the version doesn't change.
Beta Was this translation helpful? Give feedback.
All reactions