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 script fails to configure compose variables #707

New Issue
Closed
opened 2026-02-04 20:59:43 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 20:59:43 +03:00
Owner
Copy Link

Originally created by @Ingraved on GitHub (Mar 29, 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 "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/komodo.sh)"

📝 Provide a clear and concise description of the issue.

Komodo essentially runs from a Docker compose yaml file along with a compose.env file.
The 'komodo-install.sh' script is configured to create random values for DB_PASSWORD and PASSKEY on lines 68 & 69.
The script then attempts to pass those values into the compse.env file on lines 74 & 75. It fails. It also fails to set the DB_USERNAME value on line 73 as well. I did not observe any error messages when running the scrip tin verbose.
The resulting /opt/komodo/compose.env file inside komodo lxc has the default values on lines 17-22.

## DB credentials - Ignored for Sqlite
KOMODO_DB_USERNAME=admin
KOMODO_DB_PASSWORD=admin

## Configure a secure passkey to authenticate between Core / Periphery.
KOMODO_PASSKEY=a_random_passkey

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

  1. run komodo script on PVE shell
  2. select default installation
  3. choose 1. MongoDB or 2.Postgres
  4. observe lines 17-22 in /opt/komodo/compose.env within the Komodo lxc.

❌ Paste the full error output (if available).

No error message available

🖼️ Additional context (optional).

I attempted the install script on two separate systems multiple times each and the issue persisted on all of them.

Originally created by @Ingraved on GitHub (Mar 29, 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 "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/komodo.sh)" ### 📝 Provide a clear and concise description of the issue. Komodo essentially runs from a Docker compose yaml file along with a compose.env file. The 'komodo-install.sh' script is configured to create random values for `DB_PASSWORD` and `PASSKEY` on lines 68 & 69. The script then attempts to pass those values into the compse.env file on lines 74 & 75. It fails. It also fails to set the `DB_USERNAME` value on line 73 as well. I did not observe any error messages when running the scrip tin verbose. The resulting `/opt/komodo/compose.env` file inside komodo lxc has the default values on lines 17-22. ``` ## DB credentials - Ignored for Sqlite KOMODO_DB_USERNAME=admin KOMODO_DB_PASSWORD=admin ## Configure a secure passkey to authenticate between Core / Periphery. KOMODO_PASSKEY=a_random_passkey ``` ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. 1. run komodo script on PVE shell 2. select default installation 3. choose 1. MongoDB or 2.Postgres 4. observe lines 17-22 in /opt/komodo/compose.env within the Komodo lxc. ### ❌ Paste the full error output (if available). No error message available ### 🖼️ Additional context (optional). I attempted the install script on two separate systems multiple times each and the issue persisted on all of them.
OVERLORD added the bug label 2026-02-04 20:59:43 +03:00
OVERLORD commented 2026-02-04 20:59:56 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Mar 29, 2025):

Will be fixed after the merge

@tremor021 commented on GitHub (Mar 29, 2025): Will be fixed after the merge
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 bug
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#707
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?