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

Petio does not install #2000

New Issue
Closed
opened 2025-11-20 05:21:30 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 05:21:30 -05:00
Owner
Copy Link

Originally created by @toros231 on GitHub (Oct 2, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Petio

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 20.04

📈 Which Proxmox version are you on?

8.4.13

📝 Provide a clear and concise description of the issue.

I encountered an error when installing Petio using the provided Petio.sh script.
I tested both default and advanced installation modes, and the error appears in both cases.

The script forces the LXC template to Ubuntu 20.04, and the issue occurs during installation inside the container.

🔄 Steps to reproduce the issue.

The default or advanced settings give the same result.

❌ Paste the full error output (if available).

/dev/fd/63: line 336: unset: `MSG_INFO_SHOWN[Network Connected: \033[36m192.168.2.83 ]': not a valid identifier

[ERROR] in line 336: exit code 0: while executing command unset MSG_INFO_SHOWN["$msg"]

[ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

🖼️ Additional context (optional).

⚙️ Using Default Settings on node pve
🆔 Container ID: 100
🖥️ Operating System: ubuntu (20.04)
📦 Container Type: Unprivileged
💾 Disk Size: 4 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 1024 MiB
🚀 Creating a Petio LXC using the above default settings

✔️ Storage local (Free: 339.4GB Used: 21.1GB) [Template]
✔️ Storage local-zfs (Free: 339.4GB Used: 74.2GB) [Container]
✔️ Template ubuntu-20.04-standard_20.04-1_amd64.tar.gz [online]
💡 Template ubuntu-20.04-standard_20.04-1_amd64.tar.gz is missing or corrupted. Re-downloading.
✔️ Template download successful.
✔️ LXC Container 100 was successfully created.
✔️ Started LXC Container
💡 No network in LXC yet (try 1/10) – waiting...
✔️ Network in LXC is reachable (ping)
Extracting templates from packages: 100%
✔️ Customized LXC Container
✔️ Set up Container OS
✔️ Network Connected: 192.168.2.83

Originally created by @toros231 on GitHub (Oct 2, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Petio ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/petio.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 20.04 ### 📈 Which Proxmox version are you on? 8.4.13 ### 📝 Provide a clear and concise description of the issue. I encountered an error when installing Petio using the provided Petio.sh script. I tested both default and advanced installation modes, and the error appears in both cases. The script forces the LXC template to Ubuntu 20.04, and the issue occurs during installation inside the container. ### 🔄 Steps to reproduce the issue. The default or advanced settings give the same result. ### ❌ Paste the full error output (if available). /dev/fd/63: line 336: unset: `MSG_INFO_SHOWN[Network Connected: \033[36m192.168.2.83 ]': not a valid identifier [ERROR] in line 336: exit code 0: while executing command unset MSG_INFO_SHOWN["$msg"] [ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)" ### 🖼️ Additional context (optional). ⚙️ Using Default Settings on node pve 🆔 Container ID: 100 🖥️ Operating System: ubuntu (20.04) 📦 Container Type: Unprivileged 💾 Disk Size: 4 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 1024 MiB 🚀 Creating a Petio LXC using the above default settings ✔️ Storage local (Free: 339.4GB Used: 21.1GB) [Template] ✔️ Storage local-zfs (Free: 339.4GB Used: 74.2GB) [Container] ✔️ Template ubuntu-20.04-standard_20.04-1_amd64.tar.gz [online] 💡 Template ubuntu-20.04-standard_20.04-1_amd64.tar.gz is missing or corrupted. Re-downloading. ✔️ Template download successful. ✔️ LXC Container 100 was successfully created. ✔️ Started LXC Container 💡 No network in LXC yet (try 1/10) – waiting... ✔️ Network in LXC is reachable (ping) Extracting templates from packages: 100% ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.2.83
saavagebueno added the bug label 2025-11-20 05:21:30 -05:00
saavagebueno commented 2025-11-20 05:21:37 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Oct 3, 2025):

@toros231 I´m sorry but we gonna delete the script. It runs on stone old Ubuntu 20.4 and Mongo 4.4 only. Also the last release and Github activity was in March 2024.

@michelroegl-brunner commented on GitHub (Oct 3, 2025): @toros231 I´m sorry but we gonna delete the script. It runs on stone old Ubuntu 20.4 and Mongo 4.4 only. Also the last release and Github activity was in March 2024.
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#2000
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?