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

Forgejo Install Issues #944

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

Originally created by @LoadingStill on GitHub (Apr 17, 2025).

✅ Have you read and understood the above guidelines?

yes

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

forgejo

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/asylumexp/Proxmox/main/ct/forgejo.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Image

🔄 Steps to reproduce the issue.

Run install script keep default.

❌ Paste the full error output (if available).

⚙️ Using Default Settings on node pve (🔍 Verbose)
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
💾 Disk Size: 10 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🆔 Container ID: 106
🔍 Verbose Mode: Enabled
🚀 Creating a Forgejo LXC using the above default settings

✔️ Using backups for Template Storage.
✔️ Using emby for Container Storage.
✔️ LXC Template is ready to use.
✖️ Container creation failed. Checking if template is corrupted.
bash: line 280: TEMPLATE_PATH: unbound variable
✖️ Template appears to be corrupted. Removing and re-downloading.
bash: line 282: TEMPLATE_PATH: unbound variable

🖼️ Additional context (optional).

The output was the same with verbose and non verbose outputs.

Originally created by @LoadingStill on GitHub (Apr 17, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? forgejo ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/asylumexp/Proxmox/main/ct/forgejo.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. <img width="663" alt="Image" src="https://github.com/user-attachments/assets/fcd98684-5bab-48ca-a58e-38c453f2d397" /> ### 🔄 Steps to reproduce the issue. Run install script keep default. ### ❌ Paste the full error output (if available). ⚙️ Using Default Settings on node pve (🔍 Verbose) 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 💾 Disk Size: 10 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🆔 Container ID: 106 🔍 Verbose Mode: Enabled 🚀 Creating a Forgejo LXC using the above default settings ✔️ Using backups for Template Storage. ✔️ Using emby for Container Storage. ✔️ LXC Template is ready to use. ✖️ Container creation failed. Checking if template is corrupted. bash: line 280: TEMPLATE_PATH: unbound variable ✖️ Template appears to be corrupted. Removing and re-downloading. bash: line 282: TEMPLATE_PATH: unbound variable ### 🖼️ Additional context (optional). The output was the same with verbose and non verbose outputs.
saavagebueno added the bug label 2025-11-20 04:56:56 -05:00
saavagebueno commented 2025-11-20 04:56:56 -05:00
Author
Owner
Copy Link

@LoadingStill commented on GitHub (Apr 17, 2025):

I did remove all templates and let the script install everything from scratch.

@LoadingStill commented on GitHub (Apr 17, 2025): I did remove all templates and let the script install everything from scratch.
saavagebueno commented 2025-11-20 04:56:57 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 18, 2025):

Thats the arm64 Repo from @asylumexp , Not our

@MickLesk commented on GitHub (Apr 18, 2025): Thats the arm64 Repo from @asylumexp , Not our
saavagebueno commented 2025-11-20 04:56:57 -05:00
Author
Owner
Copy Link

@asylumexp commented on GitHub (Apr 18, 2025):

use local for template storage not backups

@asylumexp commented on GitHub (Apr 18, 2025): use local for template storage not backups
saavagebueno commented 2025-11-20 04:56:57 -05:00
Author
Owner
Copy Link

@LoadingStill commented on GitHub (Apr 18, 2025):

use local for template storage not backups

I will give that a shot when I get home.

But regarding arm, where would I see this is an arm install? I can follow the link in the install script and it shows amd64 everywhere and I see arm no where in there, is there something I missed?

@LoadingStill commented on GitHub (Apr 18, 2025): > use local for template storage not backups I will give that a shot when I get home. But regarding arm, where would I see this is an arm install? I can follow the link in the install script and it shows amd64 everywhere and I see arm no where in there, is there something I missed?
saavagebueno commented 2025-11-20 04:56:57 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 18, 2025):

Look at your bash call in Post 1, you are in our Repo for x86_64 Not for arm64 (@asylumexp s Repo)

@MickLesk commented on GitHub (Apr 18, 2025): Look at your bash call in Post 1, you are in our Repo for x86_64 Not for arm64 (@asylumexp s Repo)
saavagebueno commented 2025-11-20 04:56:57 -05:00
Author
Owner
Copy Link

@LoadingStill commented on GitHub (Apr 18, 2025):

I had no idea there were multiple scripts under the website as I pulled it from https://community-scripts.github.io/ProxmoxVE/ and went down the list with multiple installs in the same hour. Is there a second site that is for arm, if so would you link it please so I can keep an eye out so I don't know how I picked an arm script when the rest worked.

@LoadingStill commented on GitHub (Apr 18, 2025): I had no idea there were multiple scripts under the website as I pulled it from https://community-scripts.github.io/ProxmoxVE/ and went down the list with multiple installs in the same hour. Is there a second site that is for arm, if so would you link it please so I can keep an eye out so I don't know how I picked an arm script when the rest worked.
saavagebueno commented 2025-11-20 04:56:57 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 18, 2025):

bash -c "$(curl -fsSL https://raw.githubusercontent.com/asylumexp/Proxmox/main/ct/forgejo.sh)"

???

@MickLesk commented on GitHub (Apr 18, 2025): bash -c "$(curl -fsSL https://raw.githubusercontent.com/asylumexp/Proxmox/main/ct/forgejo.sh)" ???
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#944
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?