SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-28 00:32:47 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Jellyfin Container Creation Failed #1344

New Issue
Closed
opened 2025-11-20 05:08:31 -05:00 by saavagebueno · 12 comments
saavagebueno commented 2025-11-20 05:08:31 -05:00
Owner
Copy Link

Originally created by @wetmarble on GitHub (Jun 24, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Jellyfin Media Server

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 24.04

📝 Provide a clear and concise description of the issue.

When running the script, I get the error message:

Container creation failed. Checking if template is corrupted or incomplete.
Template is valid, but container creation still failed.

[ERROR] in line 999: 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.

  1. run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyfin.sh)" in the proxmox shell

❌ Paste the full error output (if available).

⚙️ Using Default Settings on node pve
🖥️ Operating System: ubuntu
🌟 Version: 24.04
📦 Container Type: Unprivileged
💾 Disk Size: 8 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🆔 Container ID: 109
🚀 Creating a Jellyfin LXC using the above default settings

✔️ Using local for Template Storage.
✔️ Using local-lvm for Container Storage.
✔️ LXC Template List Updated
✔️ LXC Template 'ubuntu-24.04-standard_24.04-2_amd64.tar.zst' is ready to use.
✖️ Container creation failed. Checking if template is corrupted or incomplete.
✖️ Template is valid, but container creation still failed.

[ERROR] in line 999: 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).

No response

Originally created by @wetmarble on GitHub (Jun 24, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Jellyfin Media Server ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyfin.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 24.04 ### 📝 Provide a clear and concise description of the issue. When running the script, I get the error message: Container creation failed. Checking if template is corrupted or incomplete. Template is valid, but container creation still failed. [ERROR] in line 999: 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. 1. run `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyfin.sh)"` in the proxmox shell ### ❌ Paste the full error output (if available). ⚙️ Using Default Settings on node pve 🖥️ Operating System: ubuntu 🌟 Version: 24.04 📦 Container Type: Unprivileged 💾 Disk Size: 8 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🆔 Container ID: 109 🚀 Creating a Jellyfin LXC using the above default settings ✔️ Using local for Template Storage. ✔️ Using local-lvm for Container Storage. ✔️ LXC Template List Updated ✔️ LXC Template 'ubuntu-24.04-standard_24.04-2_amd64.tar.zst' is ready to use. ✖️ Container creation failed. Checking if template is corrupted or incomplete. ✖️ Template is valid, but container creation still failed. [ERROR] in line 999: 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). _No response_
saavagebueno added the bug label 2025-11-20 05:08:31 -05:00
saavagebueno commented 2025-11-20 05:08:32 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 25, 2025):

Thats Not the Script, its before the Install running. The creation of LXC failed in this Case because maybe all ubuntu repos cannot crawled, you got massive issues in networking or blocking DNS/adblock

@MickLesk commented on GitHub (Jun 25, 2025): Thats Not the Script, its before the Install running. The creation of LXC failed in this Case because maybe all ubuntu repos cannot crawled, you got massive issues in networking or blocking DNS/adblock
saavagebueno commented 2025-11-20 05:08:32 -05:00
Author
Owner
Copy Link

@ci4ic4 commented on GitHub (Jun 25, 2025):

Any and every script I try to run on my two ProxmoxVE servers finishes with exactly the same. Something is definitely broken. I thought it was to do with my setup, but I see I am not alone.

Both my servers are on

uname -a
Linux pmox 6.14.5-1-bpo12-pve #1 SMP PREEMPT_DYNAMIC PMX 6.14.5-1~bpo12+1 (2025-05-21T15:55Z) x86_64 GNU/Linux

and

pveversion
pve-manager/8.4.1/2a5fa54a8503f96d (running kernel: 6.14.5-1-bpo12-pve)

The last attempt I had just now was with netbox.

@ci4ic4 commented on GitHub (Jun 25, 2025): Any and every script I try to run on my two ProxmoxVE servers finishes with exactly the same. Something is definitely broken. I thought it was to do with my setup, but I see I am not alone. Both my servers are on uname -a Linux pmox 6.14.5-1-bpo12-pve #1 SMP PREEMPT_DYNAMIC PMX 6.14.5-1~bpo12+1 (2025-05-21T15:55Z) x86_64 GNU/Linux and pveversion pve-manager/8.4.1/2a5fa54a8503f96d (running kernel: 6.14.5-1-bpo12-pve) The last attempt I had just now was with netbox.
saavagebueno commented 2025-11-20 05:08:32 -05:00
Author
Owner
Copy Link

@ci4ic4 commented on GitHub (Jun 25, 2025):

Another data point - in case anyone is interested. I ran the netbox.sh installation script with the default settings, it failed as before. Thinking that I might get more information about the failure, I repeated it with 'bash -xv' and it eventually finished, and after some cryptic error message on login now I have an apparently functional container. I did not make any other changes between the two runs.

@ci4ic4 commented on GitHub (Jun 25, 2025): Another data point - in case anyone is interested. I ran the netbox.sh installation script with the default settings, it failed as before. Thinking that I might get more information about the failure, I repeated it with 'bash -xv' and it eventually finished, and after some cryptic error message on login now I have an apparently functional container. I did not make any other changes between the two runs.
saavagebueno commented 2025-11-20 05:08:32 -05:00
Author
Owner
Copy Link

@wetmarble commented on GitHub (Jun 25, 2025):

I was able to successfully install an Immich LXC using the install script, but Jellyfin fails. I will try with bash -xv.

@wetmarble commented on GitHub (Jun 25, 2025): I was able to successfully install an Immich LXC using the install script, but Jellyfin fails. I will try with bash -xv.
saavagebueno commented 2025-11-20 05:08:32 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 25, 2025):

It's definitely your host. I have deployed the script several times today, even on a new VM. It runs everywhere. It does not crash at jellyfin, but already when creating the LXC. So well before the script. So I can tell you in advance that it can't be due to jellyfin. Take a look at the create_lxc, maybe you will find clues as to what is not working with your setup.

you can try this one:

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

=> run in verbose

@MickLesk commented on GitHub (Jun 25, 2025): It's definitely your host. I have deployed the script several times today, even on a new VM. It runs everywhere. It does not crash at jellyfin, but already when creating the LXC. So well before the script. So I can tell you in advance that it can't be due to jellyfin. Take a look at the create_lxc, maybe you will find clues as to what is not working with your setup. you can try this one: ```bash bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/ct/jellyfin.sh)" ``` => run in verbose
saavagebueno commented 2025-11-20 05:08:33 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 25, 2025):

uname -a Linux pmox 6.14.5-1-bpo12-pve #1 SMP PREEMPT_DYNAMIC PMX 6.14.5-1~bpo12+1 (2025-05-21T15:55Z) x86_64 GNU/Linux

what did you do with your pve? the current kernel is 6.8.4-3 or 6.8.12-11 not 6.14.5-1 ?

@MickLesk commented on GitHub (Jun 25, 2025): > uname -a Linux pmox 6.14.5-1-bpo12-pve [#1](https://github.com/community-scripts/ProxmoxVE/discussions/1) SMP PREEMPT_DYNAMIC PMX 6.14.5-1~bpo12+1 (2025-05-21T15:55Z) x86_64 GNU/Linux what did you do with your pve? the current kernel is 6.8.4-3 or 6.8.12-11 not 6.14.5-1 ?
saavagebueno commented 2025-11-20 05:08:33 -05:00
Author
Owner
Copy Link

@ci4ic4 commented on GitHub (Jun 25, 2025):

https://forum.proxmox.com/threads/opt-in-linux-6-14-kernel-for-proxmox-ve-8-available-on-test-no-subscription.164497/

@ci4ic4 commented on GitHub (Jun 25, 2025): https://forum.proxmox.com/threads/opt-in-linux-6-14-kernel-for-proxmox-ve-8-available-on-test-no-subscription.164497/
saavagebueno commented 2025-11-20 05:08:33 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 25, 2025):

https://forum.proxmox.com/threads/opt-in-linux-6-14-kernel-for-proxmox-ve-8-available-on-test-no-subscription.164497/

phew, very experimental. I can only setup an vm, i dont destroy my homelab or dev pc's for this 😄

@MickLesk commented on GitHub (Jun 25, 2025): > https://forum.proxmox.com/threads/opt-in-linux-6-14-kernel-for-proxmox-ve-8-available-on-test-no-subscription.164497/ phew, very experimental. I can only setup an vm, i dont destroy my homelab or dev pc's for this :smile:
saavagebueno commented 2025-11-20 05:08:33 -05:00
Author
Owner
Copy Link

@ci4ic4 commented on GitHub (Jun 25, 2025):

https://forum.proxmox.com/threads/opt-in-linux-6-14-kernel-for-proxmox-ve-8-available-on-test-no-subscription.164497/

phew, very experimental. I can only setup an vm, i dont destroy my homelab or dev pc's for this 😄

Fair enough, and yet, somebody still has to test it... I won't be surprised if the issue in question is related somehow to this.

@ci4ic4 commented on GitHub (Jun 25, 2025): > > https://forum.proxmox.com/threads/opt-in-linux-6-14-kernel-for-proxmox-ve-8-available-on-test-no-subscription.164497/ > > phew, very experimental. I can only setup an vm, i dont destroy my homelab or dev pc's for this 😄 Fair enough, and yet, somebody still has to test it... I won't be surprised if the issue in question is related somehow to this.
saavagebueno commented 2025-11-20 05:08:33 -05:00
Author
Owner
Copy Link

@tautomer commented on GitHub (Jun 26, 2025):

I got this problem when creating an Alpine LXC from configuration file. BTW, the script was complaining about ENABLE_TUN is unbounded, so I added ENABLE_TUN="no" to the configuration file. I am not sure what it does at all or if it results in the error.

Creation with manually typing everything works fine.

@tautomer commented on GitHub (Jun 26, 2025): I got this problem when creating an Alpine LXC from configuration file. BTW, the script was complaining about ENABLE_TUN is unbounded, so I added ENABLE_TUN="no" to the configuration file. I am not sure what it does at all or if it results in the error. Creation with manually typing everything works fine.
saavagebueno commented 2025-11-20 05:08:33 -05:00
Author
Owner
Copy Link

@ci4ic4 commented on GitHub (Jun 27, 2025):

There is another problem with these scripts - at least on some I've tried. When you go over the installation sequence, it allows you to save the setup configuration in /opt/community-scripts, but the resulting saved parameters cannot be reused unless the file is modified. In my case I had to apply a similar change:

@@ -9,17 +9,17 @@
 BRG="vmbr0"
 APT_CACHER_IP="none"
 DISABLEIP6="yes"
-PW='-password VERYSECRET'
+PW='VERYSECRET'
 SSH="yes"
 SSH_AUTHORIZED_KEY=""
 VERBOSE="yes"
 TAGS="community-script;network"
 VLAN="none"
 MTU="1500"
-GATE=",gw=192.168.0.1"
+GATE="192.168.0.1"
 SD="-searchdomain=whatever.lan"
 MAC="none"
-NS="-nameserver=192.168.0.3 192.168.0.41"
+NS="192.168.0.3"
 NET="192.168.0.8/24"
-FUSE="yes"
-
+ENABLE_FUSE="yes"
+ENABLE_TUN="yes"

(so yes, you have to add ENABLE_TUN=yes).

@ci4ic4 commented on GitHub (Jun 27, 2025): There is another problem with these scripts - at least on some I've tried. When you go over the installation sequence, it allows you to save the setup configuration in /opt/community-scripts, but the resulting saved parameters cannot be reused unless the file is modified. In my case I had to apply a similar change: ``` @@ -9,17 +9,17 @@ BRG="vmbr0" APT_CACHER_IP="none" DISABLEIP6="yes" -PW='-password VERYSECRET' +PW='VERYSECRET' SSH="yes" SSH_AUTHORIZED_KEY="" VERBOSE="yes" TAGS="community-script;network" VLAN="none" MTU="1500" -GATE=",gw=192.168.0.1" +GATE="192.168.0.1" SD="-searchdomain=whatever.lan" MAC="none" -NS="-nameserver=192.168.0.3 192.168.0.41" +NS="192.168.0.3" NET="192.168.0.8/24" -FUSE="yes" - +ENABLE_FUSE="yes" +ENABLE_TUN="yes" ``` (so yes, you have to add ENABLE_TUN=yes).
saavagebueno commented 2025-11-20 05:08:34 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 27, 2025):

That's something completely different. We can't fix the issue itself, so I'm closing it.

@MickLesk commented on GitHub (Jun 27, 2025): That's something completely different. We can't fix the issue itself, so I'm closing 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#1344
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?