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 14 Packages Projects Releases 10 Wiki Activity

Komodo LXC update error #287

New Issue
Closed
opened 2026-02-04 17:45:03 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-04 17:45:03 +03:00
Owner
Copy Link

Originally created by @pluusla on GitHub (Jan 6, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Komodo LXC

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

update

📝 Provide a clear and concise description of the issue.

There is an update for Komodo Core.

I have tried the following errors within the LXC container for the update:

“update”

bash -c “$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/komodo.sh)”

in both cases the update is not possible. Error message:


 ⠋mv: cannot stat '*.compose.yaml': No such file or directory

  ✖️ Failed to create backup of *.compose.yaml!

⚙️ What settings are you using?

  • Default Settings
  • [X ] Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Komodo LXC Container installed

Type update in the LXC Container

❌ Paste the full error output (if available).

 ⠋mv: cannot stat '*.compose.yaml': No such file or directory
  ✖️  Failed to create backup of *.compose.yaml!

🖼️ Additional context (optional).

No response

Originally created by @pluusla on GitHub (Jan 6, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Komodo LXC ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. There is an update for Komodo Core. I have tried the following errors within the LXC container for the update: “update” bash -c “$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/komodo.sh)” in both cases the update is not possible. Error message: ``` ⠋mv: cannot stat '*.compose.yaml': No such file or directory ✖️ Failed to create backup of *.compose.yaml! ``` ### ⚙️ What settings are you using? - [ ] Default Settings - [X ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Komodo LXC Container installed Type update in the LXC Container ### ❌ Paste the full error output (if available). ``` ⠋mv: cannot stat '*.compose.yaml': No such file or directory ✖️ Failed to create backup of *.compose.yaml! ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the question label 2026-02-04 17:45:03 +03:00
OVERLORD commented 2026-02-04 17:45:16 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 6, 2025):

Cant reproduce. Enter following 2 codes and comment output here

cd /opt
ls -a

/opt/komodo
ls -a

@MickLesk commented on GitHub (Jan 6, 2025): Cant reproduce. Enter following 2 codes and comment output here cd /opt ls -a /opt/komodo ls -a
OVERLORD commented 2026-02-04 17:45:26 +03:00
Author
Owner
Copy Link

@pluusla commented on GitHub (Jan 6, 2025):

Yes, I also think it's very strange, since the *.compose.yaml exists. See below:

root@komodo:/opt# ls -a . .. containerd komodo

root@komodo:/opt/komodo# ls -a . .. compose.env mongo.compose.yaml

I'm not entirely sure, but I have now stopped the crowdsec service on the container. the update then worked.

Don't quite understand why to be honest...

Sorry for the inconvenience

@pluusla commented on GitHub (Jan 6, 2025): Yes, I also think it's very strange, since the *.compose.yaml exists. See below: `root@komodo:/opt# ls -a . .. containerd komodo` `root@komodo:/opt/komodo# ls -a . .. compose.env mongo.compose.yaml` I'm not entirely sure, but I have now stopped the crowdsec service on the container. the update then worked. Don't quite understand why to be honest... Sorry for the inconvenience
OVERLORD commented 2026-02-04 17:45:40 +03:00
Author
Owner
Copy Link

@pluusla commented on GitHub (Jan 6, 2025):

closed - The error was mine

@pluusla commented on GitHub (Jan 6, 2025): closed - The error was mine
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
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label question
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#287
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?