immich: Failed to start container #1148

Closed
opened 2026-02-04 23:20:21 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @E3-Sentry on GitHub (Jun 23, 2025).

Originally assigned to: @vhsdream on GitHub.

Have you read and understood the above guidelines?

yes

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

immich

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.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.

Start script

Paste the full error output (if available).

[ERROR] in line 1058: exit code 0: while executing command pct start "$CTID"

🖼️ Additional context (optional).

No response

Originally created by @E3-Sentry on GitHub (Jun 23, 2025). Originally assigned to: @vhsdream on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? immich ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. ![Image](https://github.com/user-attachments/assets/58ca2084-a4a4-4ec8-bba5-05ab7c3e88ec) ### 🔄 Steps to reproduce the issue. Start script ### ❌ Paste the full error output (if available). [ERROR] in line 1058: exit code 0: while executing command pct start "$CTID" ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 23:20:21 +03:00
Author
Owner

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

Missconfigured Proxmox. Check your Host, something Strange on your system himself. Or you dont have an igpu, then its not available because Hardware passthrough himself to get this Script working

ls -l /dev/dri/renderD128

@MickLesk commented on GitHub (Jun 23, 2025): Missconfigured Proxmox. Check your Host, something Strange on your system himself. Or you dont have an igpu, then its not available because Hardware passthrough himself to get this Script working ls -l /dev/dri/renderD128
Author
Owner

@E3-Sentry commented on GitHub (Jun 23, 2025):

Thank you for your response. I have restarted the script, but switched to a privileged LXC container. This way, I was able to install Immich successfully. Would it be possible for you to try to reproduce this on your end?

@E3-Sentry commented on GitHub (Jun 23, 2025): Thank you for your response. I have restarted the script, but switched to a privileged LXC container. This way, I was able to install Immich successfully. Would it be possible for you to try to reproduce this on your end?
Author
Owner

@vhsdream commented on GitHub (Jun 23, 2025):

@E3-Sentry I'm curious if the device passthrough failed for you somehow. If you don't mind running an install again, as unprivileged, then check the LXC container resources panel to see if the below has appeared:

Image

What's your graphics hardware? Intel or NVIDIA?

Oh, and can you run the following on your Proxmox host:

lspci -nn | grep -Ei "3d|display|vga"
@vhsdream commented on GitHub (Jun 23, 2025): @E3-Sentry I'm curious if the device passthrough failed for you somehow. If you don't mind running an install again, as unprivileged, then check the LXC container resources panel to see if the below has appeared: ![Image](https://github.com/user-attachments/assets/0a16c8ba-c0d1-4b90-9491-3a57b4fb4f39) What's your graphics hardware? Intel or NVIDIA? Oh, and can you run the following on your Proxmox host: ``` lspci -nn | grep -Ei "3d|display|vga" ```
Author
Owner

@E3-Sentry commented on GitHub (Jun 25, 2025):

Many thanks for your response, vhsdream. As it turns out, the problem was due to a faulty NVIDIA GPU. I really appreciate everyone's support.

@E3-Sentry commented on GitHub (Jun 25, 2025): Many thanks for your response, vhsdream. As it turns out, the problem was due to a faulty NVIDIA GPU. I really appreciate everyone's support.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1148