Komodo Update Fail

[LucasJanin]

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

Hi,

I'm having trouble updating my Komodo LXC with the script.

[+] Running 3/3do
 ✔ Container komodo-periphery-1  Running                                                                                                                                      0.0s 
 ✔ Container komodo-mongo-1      Running                                                                                                                                           0.0s 
 ✔ Container komodo-core-1       Running                                                                                                                                           0.0s 
  ✔️   Updated Komodo
/dev/fd/63: line 1289: CT_TYPE: unbound variable

Fortunately, this does not affect the Komodo installation :-).
Thank you in advance for your help!

🔄 Steps to reproduce the issue.

Update an exciting installation on Debian 12
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/komodo.sh)"

❌ Paste the full error output (if available).

/dev/fd/63: line 1289: CT_TYPE: unbound variable

🖼️ Additional context (optional).

No response

[Kickbut101]

this is kind of an odd setup and install through the scripts. It should be targeting the "mongo.compose.yaml" file instead of the "compose.env" file.

Maybe this should have a change in the install script too to make it more obvious that the db.compose file is the main stack?

Files inside /opt/komodo

[tremor021]

@Kickbut101 I'm not sure whats your point? docker compose uses mongo.compose.yaml and we pass it compose.env as environment file.
Its literaly in the mongo.compose.yaml:

env_file: ./compose.env

And we know which compose file was installed, because we check for it:

msg_info "Updating ${APP}"
    COMPOSE_FILE=""
    for file in /opt/komodo/*.compose.yaml; do
        if [[ "$file" != "compose.env" ]]; then
            COMPOSE_FILE="${file#/opt/komodo/}"
            break
        fi
    done

[Kickbut101]

@Kickbut101 I'm not sure whats your point? docker compose uses mongo.compose.yaml and we pass it compose.env as environment file. Its literaly in the mongo.compose.yaml:

env_file: ./compose.env

And we know which compose file was installed, because we check for it:

msg_info "Updating ${APP}"
COMPOSE_FILE=""
for file in /opt/komodo/*.compose.yaml; do
if [[ "$file" != "compose.env" ]]; then
COMPOSE_FILE="${file#/opt/komodo/}"
break
fi
done

You're right, that's my bad I read that line as /opt/komodo/*.compose.env when I first skimmed it. Sorry!

[tremor021]

Yes, which compose file will be installed depends on user choice, but yea, we check which one it is anyway so we can update without issues.

[adn34]

I can report having the same output when trying to update komodo and the komodo version not being updated despite the output saying it is.

/dev/fd/63: line 1268: CT_TYPE: unbound variable

[mad2moons]

I can also report that I am having exactly the same error when running update.

/dev/fd/63: line 1268: CT_TYPE: unbound variable

[MickLesk]

The error can be ignored, but the update still worked. Maybe fixed next week.