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

Homeassistant container update script fails to install filebrowser #1518

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

Originally created by @smhc on GitHub (Jul 17, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Podman Home Assistant Container

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

update

⚙️ 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.

Running 'update' inside the container and attempting to install the filebrowser results in the following error:

⠧ Installing FileBrowser
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
⠼ Installing FileBrowser
[ERROR] in line 75: exit code 0: while executing command tar -xzv -C /usr/local/bin

root@homeassistant:~#

🔄 Steps to reproduce the issue.

Step 1. Install 'Podman Home Assistant Container' script
Step 2. Run 'update' in console and select 'filebrowser'

❌ Paste the full error output (if available).

⠧ Installing FileBrowser
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
⠼ Installing FileBrowser
[ERROR] in line 75: exit code 0: while executing command tar -xzv -C /usr/local/bin

🖼️ Additional context (optional).

No response

Originally created by @smhc on GitHub (Jul 17, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? ~~Podman~~ Home Assistant Container ### 📂 What was the exact command used to execute the script? update ### ⚙️ 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. Running 'update' inside the container and attempting to install the filebrowser results in the following error: ``` ⠧ Installing FileBrowser gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now ⠼ Installing FileBrowser [ERROR] in line 75: exit code 0: while executing command tar -xzv -C /usr/local/bin root@homeassistant:~# ``` ### 🔄 Steps to reproduce the issue. Step 1. Install 'Podman Home Assistant Container' script Step 2. Run 'update' in console and select 'filebrowser' ### ❌ Paste the full error output (if available). ``` ⠧ Installing FileBrowser gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now ⠼ Installing FileBrowser [ERROR] in line 75: exit code 0: while executing command tar -xzv -C /usr/local/bin ``` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:11:41 -05:00
saavagebueno commented 2025-11-20 05:11:42 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 17, 2025):

execute the script manually and look where it fails

@MickLesk commented on GitHub (Jul 17, 2025): execute the script manually and look where it fails
saavagebueno commented 2025-11-20 05:11:42 -05:00
Author
Owner
Copy Link

@smhc commented on GitHub (Jul 17, 2025):

It's failing in the tar command:

    $STD curl -fsSL https://github.com/filebrowser/filebrowser/releases/download/v2.23.0/linux-amd64-filebrowser.tar.gz | tar -xzv -C /usr/local/bin

It seems the curl download is not always working correctly. It works alright if you run it manually, but fails most of the time when run within the script. If you run it a second time sometimes it works. My connection is generally fine and I don't have these issues elsewhere.

Anyway, I realised this is exactly the same as https://community-scripts.github.io/ProxmoxVE/scripts?id=filebrowser (which seems to install more reliably). I thought it was the home assistant file browser addon given it was part of the HA scripts.

Might be an issue with the download, tar, or curl options. But happy to close this with the recommendation to use https://community-scripts.github.io/ProxmoxVE/scripts?id=filebrowser instead if someone else looks up this error.

@smhc commented on GitHub (Jul 17, 2025): It's failing in the tar command: ``` $STD curl -fsSL https://github.com/filebrowser/filebrowser/releases/download/v2.23.0/linux-amd64-filebrowser.tar.gz | tar -xzv -C /usr/local/bin ``` It seems the curl download is not always working correctly. It works alright if you run it manually, but fails most of the time when run within the script. If you run it a second time sometimes it works. My connection is generally fine and I don't have these issues elsewhere. Anyway, I realised this is exactly the same as https://community-scripts.github.io/ProxmoxVE/scripts?id=filebrowser (which seems to install more reliably). I thought it was the home assistant file browser addon given it was part of the HA scripts. Might be an issue with the download, tar, or curl options. But happy to close this with the recommendation to use https://community-scripts.github.io/ProxmoxVE/scripts?id=filebrowser instead if someone else looks up this error.
saavagebueno commented 2025-11-20 05:11:42 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 17, 2025):

which ha script do you have? podman, docker, container, core? ^^

@MickLesk commented on GitHub (Jul 17, 2025): which ha script do you have? podman, docker, container, core? ^^
saavagebueno commented 2025-11-20 05:11:43 -05:00
Author
Owner
Copy Link

@smhc commented on GitHub (Jul 17, 2025):

I originally reported using the 'podman' container as I thought that's what I had. But it turns out it is the docker container: https://community-scripts.github.io/ProxmoxVE/scripts?id=homeassistant

@smhc commented on GitHub (Jul 17, 2025): I originally reported using the 'podman' container as I thought that's what I had. But it turns out it is the docker container: https://community-scripts.github.io/ProxmoxVE/scripts?id=homeassistant
saavagebueno commented 2025-11-20 05:11:43 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 17, 2025):

All right - the script will disappear next month anyway (deprecated), so it's no longer worth adapting it

@MickLesk commented on GitHub (Jul 17, 2025): All right - the script will disappear next month anyway (deprecated), so it's no longer worth adapting it
saavagebueno commented 2025-11-20 05:11:43 -05:00
Author
Owner
Copy Link

@smhc commented on GitHub (Jul 17, 2025):

I believe it is the homeassistant-core script that will be deprecated. The 'container' script is still a valid option.

@smhc commented on GitHub (Jul 17, 2025): I believe it is the [homeassistant-core](https://community-scripts.github.io/ProxmoxVE/scripts?id=homeassistant-core) script that will be deprecated. The 'container' script is still a valid option.
saavagebueno commented 2025-11-20 05:11:43 -05:00
Author
Owner
Copy Link

@rhijjawi commented on GitHub (Jul 28, 2025):

All right - the script will disappear next month anyway (deprecated), so it's no longer worth adapting it

Speaking of, in case this is not what you were referring to, Filebrowser is now in Maintenance-only mode. My suggestion is to at least add a notice on the community scripts site.

@rhijjawi commented on GitHub (Jul 28, 2025): > All right - the script will disappear next month anyway (deprecated), so it's no longer worth adapting it Speaking of, in case this is not what you were referring to, Filebrowser is now in [Maintenance-only](https://github.com/filebrowser/filebrowser#project-status) mode. My suggestion is to at least add a notice on the community scripts site.
saavagebueno commented 2025-11-20 05:11:43 -05:00
Author
Owner
Copy Link

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

All right - the script will disappear next month anyway (deprecated), so it's no longer worth adapting it

Speaking of, in case this is not what you were referring to, Filebrowser is now in Maintenance-only mode. My suggestion is to at least add a notice on the community scripts site.

Why we need to put a notice? Maintenance mode means no new features will be worked on, only bugfixes

@tremor021 commented on GitHub (Jul 28, 2025): > > All right - the script will disappear next month anyway (deprecated), so it's no longer worth adapting it > > Speaking of, in case this is not what you were referring to, Filebrowser is now in [Maintenance-only](https://github.com/filebrowser/filebrowser?rgh-link-date=2025-07-28T22%3A30%3A20.000Z#project-status) mode. My suggestion is to at least add a notice on the community scripts site. Why we need to put a notice? Maintenance mode means no new features will be worked on, only bugfixes
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 bug
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#1518
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?