Immich script fails #1446

@umrath commented on GitHub (Jul 8, 2025):

@vhsdream idk, my work. looks like an pinning issue on the system of user.

What is the reason for creating the container privileged?

I want to be able to mount the file system via NFS.

@umrath commented on GitHub (Jul 8, 2025): > [@vhsdream](https://github.com/vhsdream) idk, my work. looks like an pinning issue on the system of user. > > What is the reason for creating the container privileged? I want to be able to mount the file system via NFS.

saavagebueno commented

@tremor021 commented on GitHub (Jul 8, 2025):

You dont need priviledged container to mount NFS.

Mount the NFS share on the host, then do a mountpoint

@tremor021 commented on GitHub (Jul 8, 2025): You dont need priviledged container to mount NFS. Mount the NFS share on the host, then do a mountpoint

saavagebueno commented

@umrath commented on GitHub (Jul 8, 2025):

You dont need priviledged container to mount NFS.

Mount the NFS share on the host, then do a mountpoint

But I do not a privileged container if I want to mount the Immich-Server somewhere else via NFS, don't I?

@umrath commented on GitHub (Jul 8, 2025): > You dont need priviledged container to mount NFS. > > Mount the NFS share on the host, then do a mountpoint But I do not a privileged container if I want to mount the Immich-Server somewhere else via NFS, don't I?

saavagebueno commented

@vhsdream commented on GitHub (Jul 8, 2025):

@umrath The privileged vs unprivileged is just noise - I think something else is the issue.

If you haven't already can you try installing again to see if this happens again? Once I am able I will need to setup a test to check if we have some dependency problem with packages from Debian Testing.

@vhsdream commented on GitHub (Jul 8, 2025): @umrath The privileged vs unprivileged is just noise - I think something else is the issue. If you haven't already can you try installing again to see if this happens again? Once I am able I will need to setup a test to check if we have some dependency problem with packages from Debian Testing.

saavagebueno commented

@umrath commented on GitHub (Jul 8, 2025):

@umrath The privileged vs unprivileged is just noise - I think something else is the issue.

If you haven't already can you try installing again to see if this happens again? Once I am able I will need to setup a test to check if we have some dependency problem with packages from Debian Testing.

Actually, the installation completed despite the error.

@umrath commented on GitHub (Jul 8, 2025): > [@umrath](https://github.com/umrath) The privileged vs unprivileged is just noise - I think something else is the issue. > > If you haven't already can you try installing again to see if this happens again? Once I am able I will need to setup a test to check if we have some dependency problem with packages from Debian Testing. Actually, the installation completed despite the error.

saavagebueno commented

@vhsdream commented on GitHub (Jul 8, 2025):

Interesting. If I were you I would not use this for production and I would run the install again.

GLIBC is a huge part of the OS and if something is off it could lead to all sorts of unpredictable behaviour.

@vhsdream commented on GitHub (Jul 8, 2025): Interesting. If I were you I would not use this for production and I would run the install again. GLIBC is a huge part of the OS and if something is off it could lead to all sorts of unpredictable behaviour.

saavagebueno commented

@MickLesk commented on GitHub (Jul 8, 2025):

maybe you try to remove the debian12 template before installig, so that pveam reload it at creating (so its the newest package).

@MickLesk commented on GitHub (Jul 8, 2025): maybe you try to remove the debian12 template before installig, so that pveam reload it at creating (so its the newest package).

saavagebueno commented

@umrath commented on GitHub (Jul 8, 2025):

Interesting. If I were you I would not use this for production and I would run the install again.

GLIBC is a huge part of the OS and if something is off it could lead to all sorts of unpredictable behaviour.

Good point.
So far, I don't see anything wrong.

maybe you try to remove the debian12 template before installig, so that pveam reload it at creating (so its the newest package).

The script did download the template itself. It wasn't present before.

@umrath commented on GitHub (Jul 8, 2025): > Interesting. If I were you I would not use this for production and I would run the install again. > > GLIBC is a huge part of the OS and if something is off it could lead to all sorts of unpredictable behaviour. Good point. So far, I don't see anything wrong. > maybe you try to remove the debian12 template before installig, so that pveam reload it at creating (so its the newest package). The script did download the template itself. It wasn't present before.

saavagebueno commented

@MickLesk commented on GitHub (Jul 8, 2025):

you never had the debian 12 template before? actually there are other log outputs if it was not available at all...

@MickLesk commented on GitHub (Jul 8, 2025): you never had the debian 12 template before? actually there are other log outputs if it was not available at all...

saavagebueno commented

@umrath commented on GitHub (Jul 8, 2025):

you never had the debian 12 template before? actually there are other log outputs if it was not available at all...

Not on this host at that location. I explicitely gave it a new template location which was empty at that time.

@umrath commented on GitHub (Jul 8, 2025): > you never had the debian 12 template before? actually there are other log outputs if it was not available at all... Not on this host at that location. I explicitely gave it a new template location which was empty at that time.

saavagebueno commented

@vhsdream commented on GitHub (Jul 8, 2025):

Hmm it might have been a fluke to be honest. I think what happened is the stack-smashing thing happened (which I've seen happen to others, no idea why, would love to find out!) and so several packages from Testing were not installed. GLibC is one of the upgrades (from 2.36 to 2.41) and since it didn't get installed it broke other things.

@vhsdream commented on GitHub (Jul 8, 2025): Hmm it might have been a fluke to be honest. I think what happened is the stack-smashing thing happened (which I've seen happen to others, no idea why, would love to find out!) and so several packages from Testing were not installed. GLibC is one of the upgrades (from 2.36 to 2.41) and since it didn't get installed it broke other things.

saavagebueno commented

@umrath commented on GitHub (Jul 8, 2025):

next try, exactly same result:

_                     _      __

()__ ___ ____ ___ ()/ /
/ / __ __ \/ __ __ / / / __
/ / / / / / / / / / / / / // / / /
/// // /// // ///___// /_/

🧩 Using Advanced Settings on node *** (redacted)
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Privileged
🔐 Root Password: ********
🆔 Container ID: 113
🏠 Hostname: immich
💾 Disk Size: 3500 GB
🧠 CPU Cores: 4
🛠️ RAM Size: 4096 MiB
🌉 Bridge: vmbr0
📡 IPv4: DHCP
📡 IPv6: SLAAC/AUTO
📡 APT-Cacher IP Address: Default
⚙️ Interface MTU Size: Default
🔍 DNS Search Domain: *** (redacted)
📡 DNS Server IP Address: Host
🏷️ Vlan: Default
📡 Tags: community-script;photos
🔑 Root SSH Access: yes
🗂️ Enable FUSE Support: yes
🔍 Verbose Mode: no
🚀 Creating a immich LXC using the above advanced settings
✔️ Validated Storage (rootdir / vztmpl).
✔️ Cluster is quorate
✔️ LXC Template List Updated
⠴ Creating LXC Container
⚙️ Configuring VAAPI passthrough for LXC container

ℹ️ VAAPI enables GPU hardware acceleration (e.g., for video transcoding in Jellyfin or Plex).

➤ Automatically mount all available VAAPI devices? [Y/n]:
✔️ Started LXC Container
✔️ Customized LXC Container
✔️ Set up Container OS
✔️ Network Connected: *** (redacted)
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
✔️ Updated Container OS
✔️ Setup uv 0.7.19
✔️ Dependencies Installed
Install OpenVINO dependencies for Intel HW-accelerated machine-learning? y/N
✔️ Setup Node.js 22
✔️ Setup PostgreSQL 16
✔️ PostgreSQL 16 installed
✔️ Setup PostgreSQL modules
✔️ Set up Postgresql Database
⠹ Installing Packages from Testing Repo*** stack smashing detected ***: terminated
/dev/fd/63: line 272: 26891 Aborted sleep 0.1
curl: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libcrypto.so.3)

[ERROR] in line 278: exit code 0: while executing command sleep 0.1
/dev/stdin: line 43: post_update_to_api: command not found
/dev/fd/63: line 139: pop_var_context: head of shell_variables not a function context
✔️ Packages from Testing Repo Installed
⠦ Compiling Custom Photo-processing Library (extreme patience)

@umrath commented on GitHub (Jul 8, 2025): next try, exactly same result: _ _ __ (_)___ ___ ____ ___ (_)____/ /_ / / __ `__ \/ __ `__ \/ / ___/ __ \ / / / / / / / / / / / / / /__/ / / / /_/_/ /_/ /_/_/ /_/ /_/_/\___/_/ /_/ 🧩 Using Advanced Settings on node *** (redacted) 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Privileged 🔐 Root Password: ******** 🆔 Container ID: 113 🏠 Hostname: immich 💾 Disk Size: 3500 GB 🧠 CPU Cores: 4 🛠️ RAM Size: 4096 MiB 🌉 Bridge: vmbr0 📡 IPv4: DHCP 📡 IPv6: SLAAC/AUTO 📡 APT-Cacher IP Address: Default ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: *** (redacted) 📡 DNS Server IP Address: Host 🏷️ Vlan: Default 📡 Tags: community-script;photos 🔑 Root SSH Access: yes 🗂️ Enable FUSE Support: yes 🔍 Verbose Mode: no 🚀 Creating a immich LXC using the above advanced settings ✔️ Validated Storage (rootdir / vztmpl). ✔️ Cluster is quorate ✔️ LXC Template List Updated ⠴ Creating LXC Container ⚙️ Configuring VAAPI passthrough for LXC container ℹ️ VAAPI enables GPU hardware acceleration (e.g., for video transcoding in Jellyfin or Plex). ➤ Automatically mount all available VAAPI devices? [Y/n]: ✔️ Started LXC Container ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: *** (redacted) ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) ✔️ Updated Container OS ✔️ Setup uv 0.7.19 ✔️ Dependencies Installed Install OpenVINO dependencies for Intel HW-accelerated machine-learning? y/N ✔️ Setup Node.js 22 ✔️ Setup PostgreSQL 16 ✔️ PostgreSQL 16 installed ✔️ Setup PostgreSQL modules ✔️ Set up Postgresql Database ⠹ Installing Packages from Testing Repo*** stack smashing detected ***: terminated /dev/fd/63: line 272: 26891 Aborted sleep 0.1 curl: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libcrypto.so.3) [ERROR] in line 278: exit code 0: while executing command sleep 0.1 /dev/stdin: line 43: post_update_to_api: command not found /dev/fd/63: line 139: pop_var_context: head of shell_variables not a function context ✔️ Packages from Testing Repo Installed ⠦ Compiling Custom Photo-processing Library (extreme patience)

saavagebueno commented

@umrath commented on GitHub (Jul 8, 2025):

Also, it always fails on the first try when there is no Debian image available:

💡 Template debian-12-standard_12.7-1_amd64.tar.zst not found or appears to be corrupted. Re-downloading.
⠹ Attempt 1: Downloading LXC template...
[2]+ Stopped bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/immich.sh)"

On the next tries it passes that steps but then fails as mentioned above.

Maybe the timeouts are super aggressive?

@umrath commented on GitHub (Jul 8, 2025): Also, it always fails on the first try when there is no Debian image available: 💡 Template debian-12-standard_12.7-1_amd64.tar.zst not found or appears to be corrupted. Re-downloading. ⠹ Attempt 1: Downloading LXC template... [2]+ Stopped bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/ct/immich.sh)" On the next tries it passes that steps but then fails as mentioned above. Maybe the timeouts are super aggressive?

saavagebueno commented

@MickLesk commented on GitHub (Jul 8, 2025):

Nope. 300s

@MickLesk commented on GitHub (Jul 8, 2025): Nope. 300s

saavagebueno commented

@vhsdream commented on GitHub (Jul 8, 2025):

@MickLesk I can confirm if you start with no Debian template then the script exits the first time when downloading.

@umrath Can you run your install again in verbose? And can you give more information about your hardware? I haven't been able to replicate your issue and I find it incredible that you can reliably repeat the stack smashing thing!

Do you have CPU microcode installed and enabled? Can we see the output of the below?

journalctl -k -g microcode
grep -m1 'bugs' /proc/cpuinfo

@vhsdream commented on GitHub (Jul 8, 2025): @MickLesk I can confirm if you start with no Debian template then the script exits the first time when downloading. <img width="1215" height="95" alt="Image" src="https://github.com/user-attachments/assets/6e3aa57b-d463-4471-b500-70c463d9592f" /> @umrath Can you run your install again in verbose? And can you give more information about your hardware? I haven't been able to replicate your issue and I find it incredible that you can reliably repeat the stack smashing thing! Do you have CPU microcode installed and enabled? Can we see the output of the below? ``` journalctl -k -g microcode grep -m1 'bugs' /proc/cpuinfo ```

saavagebueno commented

@umrath commented on GitHub (Jul 9, 2025):

journalctl -k -g microcode
grep -m1 'bugs' /proc/cpuinfo

kernel: microcode: Current revision: 0x0000001a
bugs : spectre_v1 spectre_v2 spec_store_bypass swapgs rfds bhi

I will re-run the script with verbose.

Update: verbose is so chatty that anything relevant has been scrolled out and I cannot tell whether the error has happened and what triggered it. Does the script write a log somewhere?

@umrath commented on GitHub (Jul 9, 2025): > journalctl -k -g microcode > grep -m1 'bugs' /proc/cpuinfo kernel: microcode: Current revision: 0x0000001a bugs : spectre_v1 spectre_v2 spec_store_bypass swapgs rfds bhi I will re-run the script with verbose. Update: verbose is so chatty that anything relevant has been scrolled out and I cannot tell whether the error has happened and what triggered it. Does the script write a log somewhere?

saavagebueno commented

@vhsdream commented on GitHub (Jul 9, 2025):

@umrath Not sure about an install log.

What's your CPU hardware? It looks to me that you don't have microcode updates enabled. I expect to see something like the below:

Jun 01 11:03:20 hostname kernel: microcode: Current revision: 0x0000003a
Jun 01 11:03:20 hostname kernel: microcode: Updated early from: 0x0000002c

Not sure if what's happening to you is due to this, but I think you should install microcode updates:

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

@vhsdream commented on GitHub (Jul 9, 2025): @umrath Not sure about an install log. What's your CPU hardware? It looks to me that you don't have microcode updates enabled. I expect to see something like the below: ``` Jun 01 11:03:20 hostname kernel: microcode: Current revision: 0x0000003a Jun 01 11:03:20 hostname kernel: microcode: Updated early from: 0x0000002c ``` Not sure if what's happening to you is due to this, but I think you should install microcode updates: ``` bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/microcode.sh)" ```

saavagebueno commented

@umrath commented on GitHub (Jul 9, 2025):

Actually, the microcode update seem to have fixed it.

@umrath commented on GitHub (Jul 9, 2025): Actually, the microcode update seem to have fixed it.

saavagebueno commented

@MickLesk commented on GitHub (Jul 9, 2025):

Wth, why?

@MickLesk commented on GitHub (Jul 9, 2025): Wth, why?

saavagebueno commented