starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 09:15:59 +03:00

[GH-ISSUE #3465] Komodo script fails to configure compose variables #708

New issue

Closed

opened 2026-02-26 12:46:23 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 12:46:23 +03:00

Owner

Originally created by @Ingraved on GitHub (Mar 28, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/3465

✅ 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.

run komodo script on PVE shell
select default installation
choose 1. MongoDB or 2.Postgres
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 28, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/3465 ### ✅ 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.

kerem

2026-02-26 12:46:23 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:46:24 +03:00

Author

Owner

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

Will be fixed after the merge

@tremor021 commented on GitHub (Mar 28, 2025): Will be fixed after the merge

kerem referenced this issue

2026-02-26 13:32:50 +03:00

[PR #1550] [MERGED] **READ GUIDE FIRST** breaking change: Homeassistant-Core upgrade os and python3 #3229

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#708

No description provided.

Rows
Columns