SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-08-01 10:18:51 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Watcharr Update Script exits with 'go command not found' #559

New Issue
Closed
opened 2025-11-20 04:50:10 -05:00 by saavagebueno · 5 comments
saavagebueno commented 2025-11-20 04:50:10 -05:00
Owner
Copy Link

Originally created by @Clusters on GitHub (Feb 18, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Watcharr

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

update

📝 Provide a clear and concise description of the issue.

During the update process an error appears indicating that the go command is unknown.
The issue is that the go binary is not present inside the PATH environment. I'll propose a PR for this to fix it.

Image

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

  1. install new Watcharr LXC with the command from the community-scripts website
  2. go inside the newly created container and type 'update' (you can force an update if you lower the version in /opt/Watcher_version.txt manually)
  3. wait until the error appears

❌ Paste the full error output (if available).

environment: line 51: go: command not found
[ERROR] in line 51: exit code 0: while executing command go mod download

🖼️ Additional context (optional).

No response

Originally created by @Clusters on GitHub (Feb 18, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Watcharr ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. During the update process an error appears indicating that the go command is unknown. The issue is that the go binary is not present inside the PATH environment. I'll propose a PR for this to fix it. ![Image](https://github.com/user-attachments/assets/ccab991d-eddf-4c55-a8c4-d4d77b616232) ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. 1. install new Watcharr LXC with the command from the community-scripts website 2. go inside the newly created container and type 'update' (you can force an update if you lower the version in /opt/Watcher_version.txt manually) 3. wait until the error appears ### ❌ Paste the full error output (if available). `environment: line 51: go: command not found` `[ERROR] in line 51: exit code 0: while executing command go mod download` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 04:50:10 -05:00
saavagebueno commented 2025-11-20 04:50:11 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 18, 2025):

I cant reproduce your problem. It works fine here

Image

@tremor021 commented on GitHub (Feb 18, 2025): I cant reproduce your problem. It works fine here ![Image](https://github.com/user-attachments/assets/8ae72451-7a30-4baa-91a1-563a15e653a6)
saavagebueno commented 2025-11-20 04:50:11 -05:00
Author
Owner
Copy Link

@Clusters commented on GitHub (Feb 18, 2025):

Hi @tremor021 are you using Debian12?

What does echo $PATH give you (inside the Watcharr container)?

@Clusters commented on GitHub (Feb 18, 2025): Hi @tremor021 are you using Debian12? What does `echo $PATH` give you (inside the Watcharr container)?
saavagebueno commented 2025-11-20 04:50:11 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 18, 2025):

root@watcharr:~# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

btw, if you read the install script:
ln -sf /usr/local/go/bin/go /usr/local/bin/go so its in the path
not sure what you did after the installation to break that, but its working as intended here

@tremor021 commented on GitHub (Feb 18, 2025): ``` root@watcharr:~# echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ``` btw, if you read the install script: `ln -sf /usr/local/go/bin/go /usr/local/bin/go` so its in the path not sure what you did after the installation to break that, but its working as intended here
saavagebueno commented 2025-11-20 04:50:11 -05:00
Author
Owner
Copy Link

@Clusters commented on GitHub (Feb 19, 2025):

@tremor021 have you tried to create a new LXC with the script with Default settings? I've done it several times now. All of them fail to have /usr/local/bin as well as /usr/local/sbin in their path.

Here's what I did step by step.

PVE:~$ bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/watcharr.sh)" -> Default Settings

PVE:~$ lxc enter <newly_created_container_id>

root@Watcharr:~$ go -v

which leads to the same error as mentioned above.
Can you confirm, that this does not lead to an error for you?
Can this be a Proxmox issue?

@Clusters commented on GitHub (Feb 19, 2025): @tremor021 have you tried to create a new LXC with the script with Default settings? I've done it several times now. All of them fail to have /usr/local/bin as well as /usr/local/sbin in their path. Here's what I did step by step. `PVE:~$ bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/watcharr.sh)"` -> Default Settings `PVE:~$ lxc enter <newly_created_container_id>` `root@Watcharr:~$ go -v` which leads to the same error as mentioned above. Can you confirm, that this does not lead to an error for you? Can this be a Proxmox issue?
saavagebueno commented 2025-11-20 04:50:11 -05:00
Author
Owner
Copy Link

@Clusters commented on GitHub (Feb 19, 2025):

Hi, I just set-up a new Proxmox PVE and indeed the PATH environment is different. So this seems to be some weird Proxmox related issue.
I will close this issue now and will update my PR accordingly later today (I'm currently on the go).

@Clusters commented on GitHub (Feb 19, 2025): Hi, I just set-up a new Proxmox PVE and indeed the PATH environment is different. So this seems to be some weird Proxmox related issue. I will close this issue now and will update my PR accordingly later today (I'm currently on the go).
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#559
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?