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

tailscale won't run from LXC #1717

New Issue
Closed
opened 2025-11-20 05:15:26 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:15:26 -05:00
Owner
Copy Link

Originally created by @mkaatman on GitHub (Aug 15, 2025).

✅ Have you read and understood the above guidelines?

yes

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

tailscale

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/addon/add-tailscale-lxc.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

debian LXC

📝 Provide a clear and concise description of the issue.

The page says:
" You can use it inside a running LXC container or directly on the Proxmox VE host to extend functionality with Tailscale."

But it seems the script wants to be run from the host only if I'm understanding correctly.

if ! command -v pveversion &>/dev/null; then
  msg_error "This script must be run on the Proxmox VE host (not inside an LXC container)"
  exit 1
fi

Please let me know if it's user error

🔄 Steps to reproduce the issue.

Setup debian LXC with helper scripts
Run tailscale script within that LXC

❌ Paste the full error output (if available).

✖ This script must be run on the Proxmox VE host (not inside an LXC container)

🖼️ Additional context (optional).

No response

Originally created by @mkaatman on GitHub (Aug 15, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? tailscale ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/addon/add-tailscale-lxc.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? debian LXC ### 📝 Provide a clear and concise description of the issue. The page says: " You can use it inside a running LXC container or directly on the Proxmox VE host to extend functionality with Tailscale." But it seems the script wants to be run from the host only if I'm understanding correctly. ``` if ! command -v pveversion &>/dev/null; then msg_error "This script must be run on the Proxmox VE host (not inside an LXC container)" exit 1 fi ``` Please let me know if it's user error ### 🔄 Steps to reproduce the issue. Setup debian LXC with helper scripts Run tailscale script within that LXC ### ❌ Paste the full error output (if available). ✖ This script must be run on the Proxmox VE host (not inside an LXC container) ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:15:26 -05:00
saavagebueno commented 2025-11-20 05:15:27 -05:00
Author
Owner
Copy Link

@mkaatman commented on GitHub (Aug 15, 2025):

Nevermind, I see now after studying the script some more. I run it from the host and it gives me a list of LXCs to choose from.

@mkaatman commented on GitHub (Aug 15, 2025): Nevermind, I see now after studying the script some more. I run it from the host and it gives me a list of LXCs to choose from.
saavagebueno commented 2025-11-20 05:15:27 -05:00
Author
Owner
Copy Link

@galahad42 commented on GitHub (Aug 16, 2025):

Nevermind, I see now after studying the script some more. I run it from the host and it gives me a list of LXCs to choose from.

Hey mate, I'm stuck here too. During the whiptail menu, I select a container but it keeps looping back to the menu, doesn't proceed further

@galahad42 commented on GitHub (Aug 16, 2025): > Nevermind, I see now after studying the script some more. I run it from the host and it gives me a list of LXCs to choose from. Hey mate, I'm stuck here too. During the whiptail menu, I select a container but it keeps looping back to the menu, doesn't proceed further
saavagebueno commented 2025-11-20 05:15:27 -05:00
Author
Owner
Copy Link

@mkaatman commented on GitHub (Aug 16, 2025):

Mine worked. So you see the list of containers but you pick and it asks again? Did you use the debian LXC script for the container you created? Shot in the dark, but are you hitting space to select the container before hitting enter?

@mkaatman commented on GitHub (Aug 16, 2025): Mine worked. So you see the list of containers but you pick and it asks again? Did you use the debian LXC script for the container you created? Shot in the dark, but are you hitting space to select the container before hitting enter?
saavagebueno commented 2025-11-20 05:15:27 -05:00
Author
Owner
Copy Link

@galahad42 commented on GitHub (Aug 16, 2025):

I have the ubuntu lxc, that should not be a problem ig. Also thank you, space did it!!

@galahad42 commented on GitHub (Aug 16, 2025): I have the ubuntu lxc, that should not be a problem ig. Also thank you, space did it!!
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#1717
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?