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

UpSnap #1665

New Issue
Closed
opened 2026-02-05 01:53:47 +03:00 by OVERLORD · 9 comments
OVERLORD commented 2026-02-05 01:53:47 +03:00
Owner
Copy Link

Originally created by @smibrandon on GitHub (Sep 23, 2025).

✅ Have you read and understood the above guidelines?

yes

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

UpSnap

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/8.1.10/4b06efb5db453f29 (running kernel: 6.5.13-3-pve)

📝 Provide a clear and concise description of the issue.

__ __ _____ / / / /___ / ___/____ ____ _____ / / / / __ \\__ \/ __ \/ __/ __
/ // / // // / / / / // / // /
_/ ./// //_,/ ._/
// //
⚙️ Using Default Settings on node proxmoxserver (🔍 Verbose)
🆔 Container ID: 107
🖥️ Operating System: debian (13)
📦 Container Type: Unprivileged
💾 Disk Size: 2 GB
🧠 CPU Cores: 1
🛠️ RAM Size: 512 MiB
🔍 Verbose Mode: Enabled
🚀 Creating a UpSnap LXC using the above default settings

✔️ Storage local (Free: 17.5GB Used: 18.4GB) [Template]
✔️ Storage ssd_thinpool (Free: 514.4GB Used: 395.1GB) [Container]
✔️ Template debian-13-standard_13.1-1_amd64.tar.zst [local]
✖️ Container creation failed. Checking if template is corrupted or incomplete.
✖️ Template is valid, but container creation still failed.

[ERROR] in line 1152: exit code 0: while executing command bash -c "(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" ?`

🔄 Steps to reproduce the issue.

simply running the script with either advanced or default settings

❌ Paste the full error output (if available).

__ __ _____ / / / /___ / ___/____ ____ _____ / / / / __ \\__ \/ __ \/ __/ __
/ // / // // / / / / // / // /
_/ ./// //_,/ ._/
// //
⚙️ Using Default Settings on node proxmoxserver (🔍 Verbose)
🆔 Container ID: 107
🖥️ Operating System: debian (13)
📦 Container Type: Unprivileged
💾 Disk Size: 2 GB
🧠 CPU Cores: 1
🛠️ RAM Size: 512 MiB
🔍 Verbose Mode: Enabled
🚀 Creating a UpSnap LXC using the above default settings

✔️ Storage local (Free: 17.5GB Used: 18.4GB) [Template]
✔️ Storage ssd_thinpool (Free: 514.4GB Used: 395.1GB) [Container]
✔️ Template debian-13-standard_13.1-1_amd64.tar.zst [local]
✖️ Container creation failed. Checking if template is corrupted or incomplete.
✖️ Template is valid, but container creation still failed.

[ERROR] in line 1152: exit code 0: while executing command bash -c "(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" ?`

🖼️ Additional context (optional).

Note: successfully ran and built another LXC from another script using same container ID

Originally created by @smibrandon on GitHub (Sep 23, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? UpSnap ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/upsnap.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/8.1.10/4b06efb5db453f29 (running kernel: 6.5.13-3-pve) ### 📝 Provide a clear and concise description of the issue. ` __ __ _____ / / / /___ / ___/____ ____ _____ / / / / __ \\__ \/ __ \/ __ `/ __ \ / /_/ / /_/ /__/ / / / / /_/ / /_/ / \____/ .___/____/_/ /_/\__,_/ .___/ /_/ /_/ ⚙️ Using Default Settings on node proxmoxserver (🔍 Verbose) 🆔 Container ID: 107 🖥️ Operating System: debian (13) 📦 Container Type: Unprivileged 💾 Disk Size: 2 GB 🧠 CPU Cores: 1 🛠️ RAM Size: 512 MiB 🔍 Verbose Mode: Enabled 🚀 Creating a UpSnap LXC using the above default settings ✔️ Storage local (Free: 17.5GB Used: 18.4GB) [Template] ✔️ Storage ssd_thinpool (Free: 514.4GB Used: 395.1GB) [Container] ✔️ Template debian-13-standard_13.1-1_amd64.tar.zst [local] ✖️ Container creation failed. Checking if template is corrupted or incomplete. ✖️ Template is valid, but container creation still failed. [ERROR] in line 1152: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" $?` ### 🔄 Steps to reproduce the issue. simply running the script with either advanced or default settings ### ❌ Paste the full error output (if available). ` __ __ _____ / / / /___ / ___/____ ____ _____ / / / / __ \\__ \/ __ \/ __ `/ __ \ / /_/ / /_/ /__/ / / / / /_/ / /_/ / \____/ .___/____/_/ /_/\__,_/ .___/ /_/ /_/ ⚙️ Using Default Settings on node proxmoxserver (🔍 Verbose) 🆔 Container ID: 107 🖥️ Operating System: debian (13) 📦 Container Type: Unprivileged 💾 Disk Size: 2 GB 🧠 CPU Cores: 1 🛠️ RAM Size: 512 MiB 🔍 Verbose Mode: Enabled 🚀 Creating a UpSnap LXC using the above default settings ✔️ Storage local (Free: 17.5GB Used: 18.4GB) [Template] ✔️ Storage ssd_thinpool (Free: 514.4GB Used: 395.1GB) [Container] ✔️ Template debian-13-standard_13.1-1_amd64.tar.zst [local] ✖️ Container creation failed. Checking if template is corrupted or incomplete. ✖️ Template is valid, but container creation still failed. [ERROR] in line 1152: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" $?` ### 🖼️ Additional context (optional). Note: successfully ran and built another LXC from another script using same container ID
OVERLORD added the bug label 2026-02-05 01:53:47 +03:00
OVERLORD commented 2026-02-05 01:53:54 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 23, 2025):

Upgrade your Proxmox. Your pve-container is outdated

@MickLesk commented on GitHub (Sep 23, 2025): Upgrade your Proxmox. Your pve-container is outdated
OVERLORD commented 2026-02-05 01:53:56 +03:00
Author
Owner
Copy Link

@milkywaypigstar-lord commented on GitHub (Oct 1, 2025):

I have the same issue on a newer version of Proxmox. Any suggestions?

@milkywaypigstar-lord commented on GitHub (Oct 1, 2025): I have the same issue on a newer version of Proxmox. Any suggestions?
OVERLORD commented 2026-02-05 01:54:00 +03:00
Author
Owner
Copy Link

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

The Solution is the comment above, are you trolling?

@MickLesk commented on GitHub (Oct 1, 2025): The Solution is the comment above, are you trolling?
OVERLORD commented 2026-02-05 01:54:08 +03:00
Author
Owner
Copy Link

@milkywaypigstar-lord commented on GitHub (Oct 2, 2025):

No I'm not trolling. I'm running 9.0.6 and I've ran all the commands to update all of my packages. What am I missing?

Image
@milkywaypigstar-lord commented on GitHub (Oct 2, 2025): No I'm not trolling. I'm running 9.0.6 and I've ran all the commands to update all of my packages. What am I missing? <img width="591" height="213" alt="Image" src="https://github.com/user-attachments/assets/e69d3792-943e-4b6d-97ed-e09b9f910521" />
OVERLORD commented 2026-02-05 01:54:11 +03:00
Author
Owner
Copy Link

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

Not dist Upgrade. Update pve-container

@MickLesk commented on GitHub (Oct 2, 2025): Not dist Upgrade. Update pve-container
OVERLORD commented 2026-02-05 01:54:14 +03:00
Author
Owner
Copy Link

@milkywaypigstar-lord commented on GitHub (Oct 2, 2025):

Ok how do I do that? I'm a noob when it comes to linux/proxmox and googling what you suggested didn't yield any useful results.

@milkywaypigstar-lord commented on GitHub (Oct 2, 2025): Ok how do I do that? I'm a noob when it comes to linux/proxmox and googling what you suggested didn't yield any useful results.
OVERLORD commented 2026-02-05 01:54:17 +03:00
Author
Owner
Copy Link

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

apt update
apt upgrade

Or build in WebFrontend -> Node -> Updates

@MickLesk commented on GitHub (Oct 2, 2025): apt update apt upgrade Or build in WebFrontend -> Node -> Updates
OVERLORD commented 2026-02-05 01:54:19 +03:00
Author
Owner
Copy Link

@smibrandon commented on GitHub (Oct 2, 2025):

apt update
apt upgrade

That's exactly what worked for me

@smibrandon commented on GitHub (Oct 2, 2025): >apt update >apt upgrade That's exactly what worked for me
OVERLORD commented 2026-02-05 01:54:22 +03:00
Author
Owner
Copy Link

@milkywaypigstar-lord commented on GitHub (Oct 2, 2025):

That's so weird because I've ran those commands too.

@milkywaypigstar-lord commented on GitHub (Oct 2, 2025): That's so weird because I've ran those commands too.
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#1665
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?