starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Komodo Update broken - using MongoDB #1358

New Issue
Closed
opened 2026-02-05 00:27:49 +03:00 by OVERLORD · 32 comments
OVERLORD commented 2026-02-05 00:27:49 +03:00
Owner
Copy Link

Originally created by @forke24x7 on GitHub (Jul 28, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Komodo

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/komodo.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Update from 1.17.x (in my case 1.17.4) to 18.x (newer) not possible. If I type in "Update" or re-execute the script it will instantly finish with nothing changed.
Saw a similar issue here (-> https://github.com/community-scripts/ProxmoxVE/issues/6017 ) with a solution here ( -> https://github.com/community-scripts/ProxmoxVE/discussions/5689 ). In my case there is no sqlite.compose.yaml or
postgres.compose.yaml. I'm using mongo so can't follow the guide.

🔄 Steps to reproduce the issue.

type update or re-execute the script when on 1.17.x and using mongo

❌ Paste the full error output (if available).

no error, script fails to execute / skips update

🖼️ Additional context (optional).

Image
Originally created by @forke24x7 on GitHub (Jul 28, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Komodo ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/komodo.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Update from 1.17.x (in my case 1.17.4) to 18.x (newer) not possible. If I type in "Update" or re-execute the script it will instantly finish with nothing changed. Saw a similar issue here (-> https://github.com/community-scripts/ProxmoxVE/issues/6017 ) with a solution here ( -> https://github.com/community-scripts/ProxmoxVE/discussions/5689 ). In my case there is no sqlite.compose.yaml or postgres.compose.yaml. I'm using mongo so can't follow the guide. ### 🔄 Steps to reproduce the issue. type update or re-execute the script when on 1.17.x and using mongo ### ❌ Paste the full error output (if available). no error, script fails to execute / skips update ### 🖼️ Additional context (optional). <img width="1399" height="103" alt="Image" src="https://github.com/user-attachments/assets/56bcd695-9473-4727-90c7-fe9b57b7e065" />
OVERLORD added the not a script issue label 2026-02-05 00:27:49 +03:00
OVERLORD commented 2026-02-05 00:27:57 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 28, 2025):

Where and what is the issue? Where is the verbose Output?

Its an simple curl crawling, all information Missing in your issue

@MickLesk commented on GitHub (Jul 28, 2025): Where and what is the issue? Where is the verbose Output? Its an simple curl crawling, all information Missing in your issue
OVERLORD commented 2026-02-05 00:28:03 +03:00
Author
Owner
Copy Link

@forke24x7 commented on GitHub (Jul 28, 2025):

Well, I dont see any useful information. As said, there is nothing happening when trying to update.

Image

It says updated but stays on version 1.17.4

@forke24x7 commented on GitHub (Jul 28, 2025): Well, I dont see any useful information. As said, there is nothing happening when trying to update. <img width="602" height="192" alt="Image" src="https://github.com/user-attachments/assets/f797e147-65ee-4a8d-9a8a-4e1da28edc5f" /> It says updated but stays on version 1.17.4
OVERLORD commented 2026-02-05 00:28:05 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 28, 2025):

Because they dont have updated the Files. Its an crawling from official Repo:
-> https://raw.githubusercontent.com/moghtech/komodo/main/compose/${COMPOSE_BASENAME

Report there. Its Not an issue with the Script. We can only use what exist.

@MickLesk commented on GitHub (Jul 28, 2025): Because they dont have updated the Files. Its an crawling from official Repo: -> https://raw.githubusercontent.com/moghtech/komodo/main/compose/${COMPOSE_BASENAME Report there. Its Not an issue with the Script. We can only use what exist.
OVERLORD commented 2026-02-05 00:28:10 +03:00
Author
Owner
Copy Link

@forke24x7 commented on GitHub (Jul 28, 2025):

Alright, thanks for your assistance. I'm not that deep into this stuff to notice myself, sorry for taking up your time.

@forke24x7 commented on GitHub (Jul 28, 2025): Alright, thanks for your assistance. I'm not that deep into this stuff to notice myself, sorry for taking up your time.
OVERLORD commented 2026-02-05 00:28:13 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 28, 2025):

You can try an docker compose stop, pull und start

@MickLesk commented on GitHub (Jul 28, 2025): You can try an docker compose stop, pull und start
OVERLORD commented 2026-02-05 00:28:16 +03:00
Author
Owner
Copy Link

@forke24x7 commented on GitHub (Jul 28, 2025):

Chances to break everything when I do that is about 105%, so I better don't fire commands I don't fully understand ;-)
I'll wait till Komodo fixes/updates their files to I can safely update. Thanks again 👍

@forke24x7 commented on GitHub (Jul 28, 2025): Chances to break everything when I do that is about 105%, so I better don't fire commands I don't fully understand ;-) I'll wait till Komodo fixes/updates their files to I can safely update. Thanks again 👍
OVERLORD commented 2026-02-05 00:28:20 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 28, 2025):

Better before every "update" is to do an snapshot or Backup before 😄

I Close it for now, If you have more information, feel free to add it here

@MickLesk commented on GitHub (Jul 28, 2025): Better before every "update" is to do an snapshot or Backup before :smile: I Close it for now, If you have more information, feel free to add it here
OVERLORD commented 2026-02-05 00:28:28 +03:00
Author
Owner
Copy Link

@rnaaijkens commented on GitHub (Aug 17, 2025):

@forke24x7 Any luck with the broken link? I like to update to but since I read this and see the broken link, I don't know.

@rnaaijkens commented on GitHub (Aug 17, 2025): @forke24x7 Any luck with the broken link? I like to update to but since I read this and see the broken link, I don't know.
OVERLORD commented 2026-02-05 00:28:32 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 17, 2025):

Here is no broken Link. The Script Work fine. I use this active every day

@MickLesk commented on GitHub (Aug 17, 2025): Here is no broken Link. The Script Work fine. I use this active every day
OVERLORD commented 2026-02-05 00:28:34 +03:00
Author
Owner
Copy Link

@rnaaijkens commented on GitHub (Aug 17, 2025):

@MickLesk I mean the update link: https://raw.githubusercontent.com/moghtech/komodo/main/compose/$%7BCOMPOSE_BASENAME I understand that is not maintained and was wondering if @forke24x7 made an issue for that.

@rnaaijkens commented on GitHub (Aug 17, 2025): @MickLesk I mean the update link: https://raw.githubusercontent.com/moghtech/komodo/main/compose/$%7BCOMPOSE_BASENAME I understand that is not maintained and was wondering if @forke24x7 made an issue for that.
OVERLORD commented 2026-02-05 00:28:37 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 17, 2025):

You need to Change the Name to your compose File - its Automatic in the Script

@MickLesk commented on GitHub (Aug 17, 2025): You need to Change the Name to your compose File - its Automatic in the Script
OVERLORD commented 2026-02-05 00:28:40 +03:00
Author
Owner
Copy Link

@forke24x7 commented on GitHub (Aug 17, 2025):

@forke24x7 Any luck with the broken link? I like to update to but since I read this and see the broken link, I don't know.

No, still stuck on 1.17.4
Typing "update" finishes instantly, says "Updated Komodo" but nothing changed.
I'm not intelligent enough to open proper issues as it seems, so I'll stay on 1.17.4.

In my VERY LIMITED understanding the script refers to komodo/tree/main/compose/compose.env and in that it says "COMPOSE_KOMODO_IMAGE_TAG=latest". So if I would open an issue at Komodo stating that "latest" is wrong...you know what I mean. Too complicated for my head.

@forke24x7 commented on GitHub (Aug 17, 2025): > [@forke24x7](https://github.com/forke24x7) Any luck with the broken link? I like to update to but since I read this and see the broken link, I don't know. No, still stuck on 1.17.4 Typing "update" finishes instantly, says "Updated Komodo" but nothing changed. I'm not intelligent enough to open proper issues as it seems, so I'll stay on 1.17.4. In my VERY LIMITED understanding the script refers to komodo/tree/main/compose/compose.env and in that it says "COMPOSE_KOMODO_IMAGE_TAG=latest". So if I would open an issue at Komodo stating that "latest" is wrong...you know what I mean. Too complicated for my head.
OVERLORD commented 2026-02-05 00:28:46 +03:00
Author
Owner
Copy Link

@rnaaijkens commented on GitHub (Aug 17, 2025):

Thnx @MickLesk But for someone who hasn't been involved in this kind of thing for very long, what does it look like and what needs to be changed?

@rnaaijkens commented on GitHub (Aug 17, 2025): Thnx @MickLesk But for someone who hasn't been involved in this kind of thing for very long, what does it look like and what needs to be changed?
OVERLORD commented 2026-02-05 00:28:51 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 17, 2025):

Nothing. The Script Crawl the latest Files based on your choose. It depends on there repo

@MickLesk commented on GitHub (Aug 17, 2025): Nothing. The Script Crawl the latest Files based on your choose. It depends on there repo
OVERLORD commented 2026-02-05 00:28:54 +03:00
Author
Owner
Copy Link

@rnaaijkens commented on GitHub (Aug 17, 2025):

@forke24x7 So the community script is correct but there repo is not. Therefore not the latest version is pulled. You can ask them the same as you did here why the repo is not up-to-date for the community script? I think they have a lot of installs from the community so they are willing to update. But they need to know.

@rnaaijkens commented on GitHub (Aug 17, 2025): @forke24x7 So the community script is correct but there repo is not. Therefore not the latest version is pulled. You can ask them the same as you did here why the repo is not up-to-date for the community script? I think they have a lot of installs from the community so they are willing to update. But they need to know.
OVERLORD commented 2026-02-05 00:29:00 +03:00
Author
Owner
Copy Link

@forke24x7 commented on GitHub (Aug 19, 2025):

With the update of their compose files it does something now but crashes with error

Image Cant see a "line 159" in compose file or /ct/komodo.sh so don't know what causes this.
@forke24x7 commented on GitHub (Aug 19, 2025): With the update of their compose files it does something now but crashes with error <img width="1073" height="91" alt="Image" src="https://github.com/user-attachments/assets/b1a4299b-0380-45ae-90e7-008ece2b852f" /> Cant see a "line 159" in compose file or /ct/komodo.sh so don't know what causes this.
OVERLORD commented 2026-02-05 00:29:03 +03:00
Author
Owner
Copy Link

@rnaaijkens commented on GitHub (Aug 20, 2025):

@forke24x7 I think it means this: The error message is saying that at line 159, a command finished with exit code 0 (which usually signals "success"), but the script is treating this as an error.

@rnaaijkens commented on GitHub (Aug 20, 2025): @forke24x7 I think it means this: The error message is saying that at line 159, a command finished with exit code 0 (which usually signals "success"), but the script is treating this as an error.
OVERLORD commented 2026-02-05 00:29:07 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 20, 2025):

verbose is needed for this

@MickLesk commented on GitHub (Aug 20, 2025): verbose is needed for this
OVERLORD commented 2026-02-05 00:29:13 +03:00
Author
Owner
Copy Link

@forke24x7 commented on GitHub (Aug 20, 2025):

Here you go

Image
@forke24x7 commented on GitHub (Aug 20, 2025): Here you go <img width="1938" height="131" alt="Image" src="https://github.com/user-attachments/assets/68f1e3c3-4e54-4aee-bd05-243ace4d52d4" />
OVERLORD commented 2026-02-05 00:29:16 +03:00
Author
Owner
Copy Link

@eikaramba commented on GitHub (Aug 22, 2025):

i experience the same problem. just a standard komodo installation trying to update from 1.18.4 to 1.19.0 via update

@eikaramba commented on GitHub (Aug 22, 2025): i experience the same problem. just a standard komodo installation trying to update from 1.18.4 to 1.19.0 via `update`
OVERLORD commented 2026-02-05 00:29:20 +03:00
Author
Owner
Copy Link

@eikaramba commented on GitHub (Aug 23, 2025):

after i added the line

COMPOSE_KOMODO_BACKUPS_PATH=/etc/komodo/backups

manually to my compose.env file it works. you can see that line in the official compose.env file here -> https://komo.do/docs/setup/mongo

@eikaramba commented on GitHub (Aug 23, 2025): after i added the line ``` COMPOSE_KOMODO_BACKUPS_PATH=/etc/komodo/backups ``` manually to my compose.env file it works. you can see that line in the official compose.env file here -> https://komo.do/docs/setup/mongo
OVERLORD commented 2026-02-05 00:29:24 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 23, 2025):

Can you make an PR ? I'll just forget about it until Monday ^^

@MickLesk commented on GitHub (Aug 23, 2025): Can you make an PR ? I'll just forget about it until Monday ^^
OVERLORD commented 2026-02-05 00:29:27 +03:00
Author
Owner
Copy Link

@eikaramba commented on GitHub (Aug 23, 2025):

i don't understand where unfortunately. it seems the script is pulling the latest version from github, so i guess everyone needs to add this line manually? that change was also mentioned in the breaking changes. https://github.com/moghtech/komodo/releases/tag/v1.19.0

@eikaramba commented on GitHub (Aug 23, 2025): i don't understand where unfortunately. it seems the script is pulling the latest version from github, so i guess everyone needs to add this line manually? that change was also mentioned in the breaking changes. https://github.com/moghtech/komodo/releases/tag/v1.19.0
OVERLORD commented 2026-02-05 00:29:29 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 23, 2025):

@community-scripts/contributor ping/reminder

@MickLesk commented on GitHub (Aug 23, 2025): @community-scripts/contributor ping/reminder
OVERLORD commented 2026-02-05 00:29:32 +03:00
Author
Owner
Copy Link

@forke24x7 commented on GitHub (Aug 25, 2025):

@community-scripts @community-scripts/contributor I dont want to fail at creating a PR, I'll just try to remind the change here - hope that works aswell.

@forke24x7 commented on GitHub (Aug 25, 2025): @community-scripts @community-scripts/contributor I dont want to fail at creating a PR, I'll just try to remind the change here - hope that works aswell.
OVERLORD commented 2026-02-05 00:29:34 +03:00
Author
Owner
Copy Link

@rnaaijkens commented on GitHub (Aug 25, 2025):

@forke24x7 I managed to update to 1.19.1 with these steps:

Add these line to your docker.compose.yaml (mine is mongo.compose.yaml)
' ## Store dated backups of the database - https://komo.do/docs/setup/backup'

  • ${COMPOSE_KOMODO_BACKUPS_PATH}:/backups

Add this to your .ENV file (mine is compose.env)
'# Backup directory path on host'
COMPOSE_KOMODO_BACKUPS_PATH=/opt/komodo/backups

Create a dir called "backups" in /opt/komodo/

Check if your images if they have "latest"
image: ghcr.io/moghtech/komodo-core:latest
image: ghcr.io/moghtech/komodo-periphery:latest

Pull the new images:
docker compose -p komodo -f mongo.compose.yaml --env-file compose.env pull

Restart docker (Komodo)
docker compose -p komodo -f mongo.compose.yaml --env-file compose.env up -d

This worked for me. Just a normal update kept me on 1.17.5

@rnaaijkens commented on GitHub (Aug 25, 2025): @forke24x7 I managed to update to 1.19.1 with these steps: Add these line to your docker.compose.yaml (mine is mongo.compose.yaml) ' ## Store dated backups of the database - https://komo.do/docs/setup/backup' - ${COMPOSE_KOMODO_BACKUPS_PATH}:/backups Add this to your .ENV file (mine is compose.env) '# Backup directory path on host' COMPOSE_KOMODO_BACKUPS_PATH=/opt/komodo/backups Create a dir called "backups" in /opt/komodo/ Check if your images if they have "latest" image: ghcr.io/moghtech/komodo-core:latest image: ghcr.io/moghtech/komodo-periphery:latest Pull the new images: docker compose -p komodo -f mongo.compose.yaml --env-file compose.env pull Restart docker (Komodo) docker compose -p komodo -f mongo.compose.yaml --env-file compose.env up -d This worked for me. Just a normal update kept me on 1.17.5
OVERLORD commented 2026-02-05 00:29:36 +03:00
Author
Owner
Copy Link

@stukinnear commented on GitHub (Aug 26, 2025):

Thanks rnaaijkens - worked for me.

@stukinnear commented on GitHub (Aug 26, 2025): Thanks rnaaijkens - worked for me.
OVERLORD commented 2026-02-05 00:29:38 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 26, 2025):

@forke24x7 I managed to update to 1.19.1 with these steps:

Add these line to your docker.compose.yaml (mine is mongo.compose.yaml) ' ## Store dated backups of the database - komo.do/docs/setup/backup'

  • ${COMPOSE_KOMODO_BACKUPS_PATH}:/backups

Add this to your .ENV file (mine is compose.env) '# Backup directory path on host' COMPOSE_KOMODO_BACKUPS_PATH=/opt/komodo/backups

Create a dir called "backups" in /opt/komodo/

Check if your images if they have "latest" image: ghcr.io/moghtech/komodo-core:latest image: ghcr.io/moghtech/komodo-periphery:latest

Pull the new images: docker compose -p komodo -f mongo.compose.yaml --env-file compose.env pull

Restart docker (Komodo) docker compose -p komodo -f mongo.compose.yaml --env-file compose.env up -d

This worked for me. Just a normal update kept me on 1.17.5

So unnecessary. Compose file reads .env file that is already in /opt/komodo. It by default points to /etc/komodo/backups. you dont need to alter anything. No need to touch mongo.compose.yaml or w/e you use.

The update procedure broke because they added COMPOSE_KOMODO_BACKUPS_PATH last week as required variable.

@tremor021 commented on GitHub (Aug 26, 2025): > [@forke24x7](https://github.com/forke24x7) I managed to update to 1.19.1 with these steps: > > Add these line to your docker.compose.yaml (mine is mongo.compose.yaml) ' ## Store dated backups of the database - [komo.do/docs/setup/backup](https://komo.do/docs/setup/backup)' > > * ${COMPOSE_KOMODO_BACKUPS_PATH}:/backups > > Add this to your .ENV file (mine is compose.env) '# Backup directory path on host' COMPOSE_KOMODO_BACKUPS_PATH=/opt/komodo/backups > > Create a dir called "backups" in /opt/komodo/ > > Check if your images if they have "latest" image: ghcr.io/moghtech/komodo-core:latest image: ghcr.io/moghtech/komodo-periphery:latest > > Pull the new images: docker compose -p komodo -f mongo.compose.yaml --env-file compose.env pull > > Restart docker (Komodo) docker compose -p komodo -f mongo.compose.yaml --env-file compose.env up -d > > This worked for me. Just a normal update kept me on 1.17.5 So unnecessary. Compose file reads .env file that is already in /opt/komodo. It by default points to `/etc/komodo/backups`. you dont need to alter anything. No need to touch `mongo.compose.yaml` or w/e you use. The update procedure broke because they added `COMPOSE_KOMODO_BACKUPS_PATH` last week as required variable.
OVERLORD commented 2026-02-05 00:29:40 +03:00
Author
Owner
Copy Link

@rnaaijkens commented on GitHub (Aug 26, 2025):

@tremor021 For me it was necessary because these lines were not in my .env or compose. So not unnecessary if you ask me.

@rnaaijkens commented on GitHub (Aug 26, 2025): @tremor021 For me it was necessary because these lines were not in my .env or compose. So not unnecessary if you ask me.
OVERLORD commented 2026-02-05 00:29:44 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 26, 2025):

Unnecessary because you are altering compose file, which you dont need to and you are creating directories you dont need to
Just run our update script, it adds the variable to the env file and all your existing configuration is intact...

@tremor021 commented on GitHub (Aug 26, 2025): Unnecessary because you are altering compose file, which you dont need to and you are creating directories you dont need to Just run our update script, it adds the variable to the env file and all your existing configuration is intact...
OVERLORD commented 2026-02-05 00:29:47 +03:00
Author
Owner
Copy Link

@rnaaijkens commented on GitHub (Aug 26, 2025):

@tremor021 This was before your update! Now it works as you are telling.

@rnaaijkens commented on GitHub (Aug 26, 2025): @tremor021 This was before your update! Now it works as you are telling.
OVERLORD commented 2026-02-05 00:29:53 +03:00
Author
Owner
Copy Link

@xkpx64 commented on GitHub (Aug 27, 2025):

https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/alpine-komodo.sh
Also need the fix for COMPOSE_KOMODO_BACKUPS_PATH

@xkpx64 commented on GitHub (Aug 27, 2025): https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/alpine-komodo.sh Also need the fix for `COMPOSE_KOMODO_BACKUPS_PATH`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1358
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?