SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Baikal: missing composer when running update script #1493

New Issue
Closed
opened 2025-11-20 05:11:21 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:11:21 -05:00
Owner
Copy Link

Originally created by @dacagi on GitHub (Jul 14, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Baikal

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

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

⚙️ What settings are you using?

* [x]  Default Settings
* [ ]  Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

As commented in #5944 I believe I experienced a side-effect of the latest changes in the install/update scripts. It looks like the update script conflicts with an existing installation.

I managed to resolve it by removing the broken install because of the failed update, and restoring the backup directory, but I'm still wondering if I will be able to update the app in the future.

If further details to reproduce are needed, I guess I could clone my LXC and run the update again to see if it happens.

🔄 Steps to reproduce the issue.

Have a working Baikal install. Run /usr/bin/update script.

🖼️ Additional context (optional).

This issue, or i think a related one, happened when I run an update on an existing Baikal installation. Totally unnecessary because it was already latest version, but I have an automation setup and I noticed because I couldn't access the service anymore.

Running update got the latest baikal.sh script and then stopped because on line 49 it couldn't find the composer file. Update failed and service didn't restart and remained faulty.

I can see a composer dir exists in the /opt/baikal-backup/vendor dir, although /opt/baikal looks very much different. I can't find no composer executable anywhere.

root@baikal:/opt# ls -l baikal
total 72
-rwxr-xr-x 1 www-data www-data  1415 Jul 14 15:17 composer.json
drwxr-xr-x 2 www-data www-data  4096 Jul 14 15:17 config
drwxr-xr-x 4 www-data www-data  4096 Jul 14 15:17 Core
drwxr-xr-x 4 www-data www-data  4096 Jul 14 15:17 html
-rwxr-xr-x 1 www-data www-data 35135 Jul 14 15:17 LICENSE
-rwxr-xr-x 1 www-data www-data  1140 Jul 14 15:17 Makefile
-rwxr-xr-x 1 www-data www-data   704 Jul 14 15:17 phpstan.neon
-rwxr-xr-x 1 www-data www-data  1414 Jul 14 15:17 README.md
-rwxr-xr-x 1 www-data www-data   227 Jul 14 15:17 SECURITY.md
drwxr-xr-x 3 www-data www-data  4096 Jul 14 15:17 Specific

root@baikal:/opt# ls -l baikal-backup/
total 60
drwxr-xr-x 2 www-data www-data  4096 Apr 17 16:19 config
drwxr-xr-x 4 www-data www-data  4096 Nov 10  2024 Core
drwxr-xr-x 4 www-data www-data  4096 Nov 30  2022 html
-rwxr-xr-x 1 www-data www-data 35135 Sep 28  2020 LICENSE
-rwxr-xr-x 1 www-data www-data  1414 Jul 27  2024 README.md
drwxr-xr-x 3 www-data www-data  4096 Apr 22 11:42 Specific
drwxr-xr-x 8 www-data www-data  4096 Nov 10  2024 vendor

I was trying to pinpoint the cause to restore my host, and then I found this PR #5947. Just wanted to ensure that this change doesn't break other existing installations via updates. I'm at a tough spot and don't know what to do, wouldn't like anyone else to experience the same.

I'm currently trying to complete the steps missing during the previous run from the scripts, and I'm now getting even more issues. I manually installed composer following the setup_composer function from tools.func and then tried running composer install again, but got following errors.

Composer is operating significantly slower than normal because you do not have the PHP curl extension enabled.
No composer.lock file present. Updating dependencies to latest instead of installing from lock file. See https://getcomposer.org/install for more information.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires sabre/dav ~4.7.0 -> satisfiable by sabre/dav[4.7.0].
    - sabre/dav 4.7.0 requires sabre/http ^5.0.5 -> satisfiable by sabre/http[5.0.5, ..., 5.1.12].
    - sabre/http 5.0.5 requires php ^7.0 -> your php version (8.2.28) does not satisfy that requirement.
    - sabre/http 5.1.0 requires php ^7.1 -> your php version (8.2.28) does not satisfy that requirement.
    - sabre/http[5.1.1, ..., 5.1.12] require ext-curl * -> it is missing from your system. Install or enable PHP's curl extension.

Originally posted by @dacagi in #5944

Originally created by @dacagi on GitHub (Jul 14, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Baikal ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/baikal.sh)" ### ⚙️ What settings are you using? * [x] Default Settings * [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. As commented in #5944 I believe I experienced a side-effect of the latest changes in the install/update scripts. It looks like the update script conflicts with an existing installation. I managed to resolve it by removing the broken install because of the failed update, and restoring the backup directory, but I'm still wondering if I will be able to update the app in the future. If further details to reproduce are needed, I guess I could clone my LXC and run the update again to see if it happens. ### 🔄 Steps to reproduce the issue. Have a working Baikal install. Run /usr/bin/update script. ### 🖼️ Additional context (optional). > This issue, or i think a related one, happened when I run an update on an existing Baikal installation. Totally unnecessary because it was already latest version, but I have an automation setup and I noticed because I couldn't access the service anymore. > > Running update got the latest [baikal.sh](https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/baikal.sh) script and then stopped because on line 49 it couldn't find the composer file. Update failed and service didn't restart and remained faulty. > > I can see a composer dir exists in the `/opt/baikal-backup/vendor` dir, although `/opt/baikal` looks very much different. I can't find no composer executable anywhere. > > ``` > root@baikal:/opt# ls -l baikal > total 72 > -rwxr-xr-x 1 www-data www-data 1415 Jul 14 15:17 composer.json > drwxr-xr-x 2 www-data www-data 4096 Jul 14 15:17 config > drwxr-xr-x 4 www-data www-data 4096 Jul 14 15:17 Core > drwxr-xr-x 4 www-data www-data 4096 Jul 14 15:17 html > -rwxr-xr-x 1 www-data www-data 35135 Jul 14 15:17 LICENSE > -rwxr-xr-x 1 www-data www-data 1140 Jul 14 15:17 Makefile > -rwxr-xr-x 1 www-data www-data 704 Jul 14 15:17 phpstan.neon > -rwxr-xr-x 1 www-data www-data 1414 Jul 14 15:17 README.md > -rwxr-xr-x 1 www-data www-data 227 Jul 14 15:17 SECURITY.md > drwxr-xr-x 3 www-data www-data 4096 Jul 14 15:17 Specific > > root@baikal:/opt# ls -l baikal-backup/ > total 60 > drwxr-xr-x 2 www-data www-data 4096 Apr 17 16:19 config > drwxr-xr-x 4 www-data www-data 4096 Nov 10 2024 Core > drwxr-xr-x 4 www-data www-data 4096 Nov 30 2022 html > -rwxr-xr-x 1 www-data www-data 35135 Sep 28 2020 LICENSE > -rwxr-xr-x 1 www-data www-data 1414 Jul 27 2024 README.md > drwxr-xr-x 3 www-data www-data 4096 Apr 22 11:42 Specific > drwxr-xr-x 8 www-data www-data 4096 Nov 10 2024 vendor > ``` > > I was trying to pinpoint the cause to restore my host, and then I found this PR #5947. Just wanted to ensure that this change doesn't break other existing installations via updates. I'm at a tough spot and don't know what to do, wouldn't like anyone else to experience the same. > > I'm currently trying to complete the steps missing during the previous run from the scripts, and I'm now getting even more issues. I manually installed composer following the `setup_composer` function from `tools.func` and then tried running `composer install` again, but got following errors. > > ``` > Composer is operating significantly slower than normal because you do not have the PHP curl extension enabled. > No composer.lock file present. Updating dependencies to latest instead of installing from lock file. See https://getcomposer.org/install for more information. > Loading composer repositories with package information > Updating dependencies > Your requirements could not be resolved to an installable set of packages. > > Problem 1 > - Root composer.json requires sabre/dav ~4.7.0 -> satisfiable by sabre/dav[4.7.0]. > - sabre/dav 4.7.0 requires sabre/http ^5.0.5 -> satisfiable by sabre/http[5.0.5, ..., 5.1.12]. > - sabre/http 5.0.5 requires php ^7.0 -> your php version (8.2.28) does not satisfy that requirement. > - sabre/http 5.1.0 requires php ^7.1 -> your php version (8.2.28) does not satisfy that requirement. > - sabre/http[5.1.1, ..., 5.1.12] require ext-curl * -> it is missing from your system. Install or enable PHP's curl extension. > ``` _Originally posted by @dacagi in [#5944](https://github.com/community-scripts/ProxmoxVE/issues/5944#issuecomment-3069984860)_
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1493
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?