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

xcaddy failing because of /usr/local/sbin not on path #1802

New Issue
Closed
opened 2026-02-05 02:18:02 +03:00 by OVERLORD · 6 comments
OVERLORD commented 2026-02-05 02:18:02 +03:00
Owner
Copy Link

Originally created by @ccoles146 on GitHub (Oct 15, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Caddy

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

8.3.0

📝 Provide a clear and concise description of the issue.

The xcaddy script does not work because of go be installed to /usr/local/sbin which does not appear in the PATH. This is very similar to
issue 7157

This could be an issue in misc/tools.func under setup_go
Or it may be more fundamental in the container setup if it turns out that /usr/local/sbin is used in several scripts.

I have confirmed that modifying the path resolves the problem.
I don't know if there's anyway to have xcaddy copy the new binary to /bin so that it just works, but that's an xcaddy issue.

🔄 Steps to reproduce the issue.

  1. install caddy using script.
  2. use defaults except also install xcaddy
  3. attempt to use xcaddy via the suggested script on the Caddy page

❌ Paste the full error output (if available).

I don't remember exactly something like go not found in $PATH

🖼️ Additional context (optional).

No response

Originally created by @ccoles146 on GitHub (Oct 15, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Caddy ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/caddy.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 8.3.0 ### 📝 Provide a clear and concise description of the issue. The xcaddy script does not work because of go be installed to /usr/local/sbin which does not appear in the PATH. This is very similar to [issue 7157](https://github.com/community-scripts/ProxmoxVE/issues/7157#issue-3349704174) This could be an issue in misc/tools.func under setup_go Or it may be more fundamental in the container setup if it turns out that /usr/local/sbin is used in several scripts. I have confirmed that modifying the path resolves the problem. I don't know if there's anyway to have xcaddy copy the new binary to /bin so that it just works, but that's an xcaddy issue. ### 🔄 Steps to reproduce the issue. 1. install caddy using script. 2. use defaults except also install xcaddy 3. attempt to use xcaddy via the suggested script on the Caddy [page](https://community-scripts.github.io/ProxmoxVE/scripts?id=caddy) ### ❌ Paste the full error output (if available). I don't remember exactly something like go not found in $PATH ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 02:18:02 +03:00
OVERLORD commented 2026-02-05 02:18:05 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 15, 2025):

With ssh or in Proxmox Terminal?

@MickLesk commented on GitHub (Oct 15, 2025): With ssh or in Proxmox Terminal?
OVERLORD commented 2026-02-05 02:18:07 +03:00
Author
Owner
Copy Link

@ccoles146 commented on GitHub (Oct 15, 2025):

I ssh into Proxmox and then use pct enter to get to the caddy container shell where I issue the xcaddy command.

@ccoles146 commented on GitHub (Oct 15, 2025): I ssh into Proxmox and then use pct enter to get to the caddy container shell where I issue the xcaddy command.
OVERLORD commented 2026-02-05 02:18:11 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 15, 2025):

Thats the issue Here, PCT enter doesnt load all correctly. My Install work because its directly in LXC. Thats the reason for getting the Info with ssh detection and Not all function Work in this case

@MickLesk commented on GitHub (Oct 15, 2025): Thats the issue Here, PCT enter doesnt load all correctly. My Install work because its directly in LXC. Thats the reason for getting the Info with ssh detection and Not all function Work in this case
OVERLORD commented 2026-02-05 02:18:14 +03:00
Author
Owner
Copy Link

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

When you run pct enter <CTID> in Proxmox, you’re not logging in through a real login shell — you’re attaching your current process to the container’s namespaces. This means that:

  • No login/profile scripts are executed
    pct enter does not run /etc/profile, ~/.bashrc, or ~/.profile. Those files are normally responsible for setting up PATH and other environment variables.
  • Minimal environment is passed
    Proxmox deliberately sanitizes the environment when attaching with pct enter. It only provides a very limited set of variables (HOME, TERM, maybe LANG), so the container's init system or shell startup files
@tremor021 commented on GitHub (Oct 18, 2025): When you run `pct enter <CTID>` in Proxmox, you’re not logging in through a real login shell — you’re attaching your current process to the container’s namespaces. This means that: - No login/profile scripts are executed `pct enter` does not run `/etc/profile`, `~/.bashrc`, or `~/.profile`. Those files are normally responsible for setting up PATH and other environment variables. - Minimal environment is passed Proxmox deliberately sanitizes the environment when attaching with pct enter. It only provides a very limited set of variables (HOME, TERM, maybe LANG), so the container's init system or shell startup files
OVERLORD commented 2026-02-05 02:18:17 +03:00
Author
Owner
Copy Link

@ccoles146 commented on GitHub (Oct 21, 2025):

Thanks for the help, I didn't realise that about pct enter. I'll bear it in mind for the future.

@ccoles146 commented on GitHub (Oct 21, 2025): Thanks for the help, I didn't realise that about pct enter. I'll bear it in mind for the future.
OVERLORD commented 2026-02-05 02:18:18 +03:00
Author
Owner
Copy Link

@tylerdotrar commented on GitHub (Dec 19, 2025):

While it might be obvious to those who read the above comments, just wanted to mention to anyone who finds this thread in the future:

TL;DR:

  • When using pct enter into an LXC, to fix the missing paths simply run sudo su -- this gives you a proper login session.
@tylerdotrar commented on GitHub (Dec 19, 2025): While it might be obvious to those who read the above comments, just wanted to mention to anyone who finds this thread in the future: **TL;DR:** - When using `pct enter` into an LXC, to fix the missing paths simply run `sudo su` -- this gives you a proper login session.
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 bug
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#1802
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?