SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-05-12 19:22:12 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Home Assistant Container LXC update issue #523

New Issue
Closed
opened 2025-11-20 04:49:37 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 04:49:37 -05:00
Owner
Copy Link

Originally created by @FredericMa on GitHub (Feb 12, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Home Assistant Container LXC

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

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

📝 Provide a clear and concise description of the issue.

I've tried updating my Home Assistant instance and encountered the error in the screenshot below.
Last week it was still working fine.
I've tried updating all packages by executing apt-get update and apt-get upgrade but it didn't make any difference.

Image

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 11

🔄 Steps to reproduce the issue.

Run the update command in the LXC.

❌ Paste the full error output (if available).

Image

🖼️ Additional context (optional).

No response

Originally created by @FredericMa on GitHub (Feb 12, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Home Assistant Container LXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/homeassistant.sh)" ### 📝 Provide a clear and concise description of the issue. I've tried updating my Home Assistant instance and encountered the error in the screenshot below. Last week it was still working fine. I've tried updating all packages by executing `apt-get update` and `apt-get upgrade` but it didn't make any difference. ![Image](https://github.com/user-attachments/assets/3129d523-cb2c-4a67-9ac4-712fb344b096) ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 11 ### 🔄 Steps to reproduce the issue. Run the update command in the LXC. ### ❌ Paste the full error output (if available). ![Image](https://github.com/user-attachments/assets/3129d523-cb2c-4a67-9ac4-712fb344b096) ### 🖼️ Additional context (optional). _No response_
saavagebueno commented 2025-11-20 04:49:38 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 12, 2025):

@genehand #2160

@MickLesk commented on GitHub (Feb 12, 2025): @genehand #2160
saavagebueno commented 2025-11-20 04:49:38 -05:00
Author
Owner
Copy Link

@genehand commented on GitHub (Feb 12, 2025):

Ah turns out that's a new option and the runlike command doesn't automatically get upgraded, that explains why people weren't running into it before. @FredericMa I put in a new PR, for now if you run this in the container the update script should work again:

pip install -U runlike

@genehand commented on GitHub (Feb 12, 2025): Ah turns out that's a new option and the `runlike` command doesn't automatically get upgraded, that explains why people weren't running into it before. @FredericMa I put in a new PR, for now if you run this in the container the update script should work again: `pip install -U runlike`
saavagebueno commented 2025-11-20 04:49:39 -05:00
Author
Owner
Copy Link

@FredericMa commented on GitHub (Feb 13, 2025):

Thanks for the help guys!
The follow up PR fixed the issue.

@FredericMa commented on GitHub (Feb 13, 2025): Thanks for the help guys! The follow up PR fixed the issue.
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#523
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?