[GH-ISSUE #6836] Immich unsupported debian version '14'

kerem commented

2026-02-26 12:48:58 +03:00

Owner

Originally created by @nathanjcollins on GitHub (Aug 14, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/6836

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.

Using proxmox 9, I use the install script for Immich. After restarting the container, I get the error unsupported debian version '14'

🔄 Steps to reproduce the issue.

Step 1 - run script detailed above
Step 2- container is running fine
Step 3 - restart container

❌ Paste the full error output (if available).

root@proxmox:~# pct start 100 --debug
run_buffer: 571 Script exited with status 25
lxc_init: 845 Failed to run lxc.hook.pre-start for container "100"
__lxc_start: 2034 Failed to initialize container "100"
0 hostid 100000 range 65536
INFO lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
INFO utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "100", config section "lxc"
DEBUG utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start produced output: unsupported debian version '14'

ERROR utils - ../src/lxc/utils.c:run_buffer:571 - Script exited with status 25
ERROR start - ../src/lxc/start.c:lxc_init:845 - Failed to run lxc.hook.pre-start for container "100"
ERROR start - ../src/lxc/start.c:__lxc_start:2034 - Failed to initialize container "100"
INFO utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "100", config section "lxc"
startup for container '100' failed
root@proxmox:~#

🖼️ Additional context (optional).

No response

Originally created by @nathanjcollins on GitHub (Aug 14, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/6836 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? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Using proxmox 9, I use the install script for Immich. After restarting the container, I get the error unsupported debian version '14' ### 🔄 Steps to reproduce the issue. Step 1 - run script detailed above Step 2- container is running fine Step 3 - restart container ### ❌ Paste the full error output (if available). root@proxmox:~# pct start 100 --debug run_buffer: 571 Script exited with status 25 lxc_init: 845 Failed to run lxc.hook.pre-start for container "100" __lxc_start: 2034 Failed to initialize container "100" 0 hostid 100000 range 65536 INFO lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor INFO utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "100", config section "lxc" DEBUG utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start produced output: unsupported debian version '14' ERROR utils - ../src/lxc/utils.c:run_buffer:571 - Script exited with status 25 ERROR start - ../src/lxc/start.c:lxc_init:845 - Failed to run lxc.hook.pre-start for container "100" ERROR start - ../src/lxc/start.c:__lxc_start:2034 - Failed to initialize container "100" INFO utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "100", config section "lxc" startup for container '100' failed root@proxmox:~# ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:48:58 +03:00

closed this issue
added the
question
label

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@MickLesk commented on GitHub (Aug 14, 2025):

Wtf. This does not look like an error in our script, but in your host. Add a screenshot here please

@MickLesk commented on GitHub (Aug 14, 2025): Wtf. This does not look like an error in our script, but in your host. Add a screenshot here please

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 14, 2025):

@MickLesk I'm not so sure - there's a weird hack I've had to do in the install script to trick it into thinking it's a vanilla Debian 12 - perhaps on PVE 9 I need to trick it to believe it's 13?

Because enabling the Testing repo has some weird effects.

@nathanjcollins can you do a cat /etc/issue and cat /etc/os-release and provide the output for starters?

Oh boy, here's mine, and I'm still on PVE8.4:

root@immich:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.0
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
VERSION_ID=12

@vhsdream commented on GitHub (Aug 14, 2025): @MickLesk I'm not so sure - there's a weird hack I've had to do in the install script to trick it into thinking it's a vanilla Debian 12 - perhaps on PVE 9 I need to trick it to believe it's 13? Because enabling the Testing repo has some weird effects. @nathanjcollins can you do a `cat /etc/issue` and `cat /etc/os-release` and provide the output for starters? Oh boy, here's mine, and I'm still on PVE8.4: ``` root@immich:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 13 (trixie)" NAME="Debian GNU/Linux" VERSION_ID="13" VERSION="13 (trixie)" VERSION_CODENAME=trixie DEBIAN_VERSION_FULL=13.0 ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" VERSION_ID=12 ```

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@Mithias-uk commented on GitHub (Aug 14, 2025):

Apologies - created my other issue as wasn't sure if it was an exact dupe of this but happy for it to be closed if you think it is, all the relevant info is in there :-)

@Mithias-uk commented on GitHub (Aug 14, 2025): Apologies - created my other issue as wasn't sure if it was an *exact* dupe of this but happy for it to be closed if you think it is, all the relevant info is in there :-)

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@nathanjcollins commented on GitHub (Aug 14, 2025):

@MickLesk I'm not so sure - there's a weird hack I've had to do in the install script to trick it into thinking it's a vanilla Debian 12 - perhaps on PVE 9 I need to trick it to believe it's 13?

Because enabling the Testing repo has some weird effects.

@nathanjcollins can you do a cat /etc/issue and cat /etc/os-release and provide the output for starters?

Oh boy, here's mine, and I'm still on PVE8.4:
root@immich:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.0
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
VERSION_ID=12

Here is what I get for those:

root@proxmox:~# cat /etc/issue

------------------------------------------------------------------------------

Welcome to the Proxmox Virtual Environment. Please use your web browser to 
configure this server - connect to:

  https://192.168.127.7:8006/

------------------------------------------------------------------------------

root@proxmox:~# cat /etc/os-release 
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.0
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@proxmox:~#

It's a brand new install of proxmox. I installed proxmox 8 and updated to 9 after I first saw this issue in the hopes that it would fix it. Weirdly I installed proxmox on another device a couple of weeks ago and did not have this issue

@nathanjcollins commented on GitHub (Aug 14, 2025): > [@MickLesk](https://github.com/MickLesk) I'm not so sure - there's a weird hack I've had to do in the install script to trick it into thinking it's a vanilla Debian 12 - perhaps on PVE 9 I need to trick it to believe it's 13? > > Because enabling the Testing repo has some weird effects. > > [@nathanjcollins](https://github.com/nathanjcollins) can you do a `cat /etc/issue` and `cat /etc/os-release` and provide the output for starters? > > Oh boy, here's mine, and I'm still on PVE8.4: > > ``` > root@immich:~# cat /etc/os-release > PRETTY_NAME="Debian GNU/Linux 13 (trixie)" > NAME="Debian GNU/Linux" > VERSION_ID="13" > VERSION="13 (trixie)" > VERSION_CODENAME=trixie > DEBIAN_VERSION_FULL=13.0 > ID=debian > HOME_URL="https://www.debian.org/" > SUPPORT_URL="https://www.debian.org/support" > BUG_REPORT_URL="https://bugs.debian.org/" > VERSION_ID=12 > ``` Here is what I get for those: ``` root@proxmox:~# cat /etc/issue ------------------------------------------------------------------------------ Welcome to the Proxmox Virtual Environment. Please use your web browser to configure this server - connect to: https://192.168.127.7:8006/ ------------------------------------------------------------------------------ root@proxmox:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 13 (trixie)" NAME="Debian GNU/Linux" VERSION_ID="13" VERSION="13 (trixie)" VERSION_CODENAME=trixie DEBIAN_VERSION_FULL=13.0 ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" root@proxmox:~# ``` It's a brand new install of proxmox. I installed proxmox 8 and updated to 9 after I first saw this issue in the hopes that it would fix it. Weirdly I installed proxmox on another device a couple of weeks ago and did not have this issue

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 14, 2025):

@nathanjcollins - I meant from inside the Immich LXC. Sorry for the confusion. But you are saying that this Immich issue happened on PVE8? I'm scared to reboot my LXC now.

@vhsdream commented on GitHub (Aug 14, 2025): @nathanjcollins - I meant from inside the Immich LXC. Sorry for the confusion. But you are saying that this Immich issue happened on PVE8? I'm scared to reboot my LXC now.

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@MickLesk commented on GitHub (Aug 14, 2025):

Did you get any Issues on Host If you Execute pve8to9? Or apt-get update & apt-get upgrade?

@MickLesk commented on GitHub (Aug 14, 2025): Did you get any Issues on Host If you Execute pve8to9? Or apt-get update & apt-get upgrade?

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@nathanjcollins commented on GitHub (Aug 14, 2025):

@nathanjcollins - I meant from inside the Immich LXC. Sorry for the confusion. But you are saying that this Immich issue happened on PVE8? I'm scared to reboot my LXC now.

root@immich:~# cat /etc/issue
Debian GNU/Linux forky/sid \n \l

root@immich:~# cat /etc/os-release

PRETTY_NAME="Debian GNU/Linux forky/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=forky
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
VERSION_ID=12
root@immich:~

Did you get any Issues on Host If you Execute pve8to9? Or apt-get update & apt-get upgrade?

I had one to remove systemd-boot, but I had done that and then performed the upgrade

@nathanjcollins commented on GitHub (Aug 14, 2025): > [@nathanjcollins](https://github.com/nathanjcollins) - I meant from inside the Immich LXC. Sorry for the confusion. But you are saying that this Immich issue happened on PVE8? I'm scared to reboot my LXC now. root@immich:~# cat /etc/issue Debian GNU/Linux forky/sid \n \l root@immich:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux forky/sid" NAME="Debian GNU/Linux" VERSION_CODENAME=forky ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" VERSION_ID=12 root@immich:~ > Did you get any Issues on Host If you Execute pve8to9? Or apt-get update & apt-get upgrade? I had one to remove systemd-boot, but I had done that and then performed the upgrade

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@MickLesk commented on GitHub (Aug 14, 2025):

Puh, it uses the sid (14) Backport instead Trixie (13).

@vhsdream maybe its General better to build immich on top of an 24.04 Ubuntu?

@MickLesk commented on GitHub (Aug 14, 2025): Puh, it uses the sid (14) Backport instead Trixie (13). @vhsdream maybe its General better to build immich on top of an 24.04 Ubuntu?

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 14, 2025):

@MickLesk I dunno about that - the devs themselves have said Immich base is Debian, and I can't imagine the nightmare of how to manage a wave of people on our Debian version suddenly having to convert their installs to Ubuntu.

@vhsdream commented on GitHub (Aug 14, 2025): @MickLesk I dunno about that - the devs themselves have said Immich base is Debian, and I can't imagine the nightmare of how to manage a wave of people on our Debian version suddenly having to convert their installs to Ubuntu.

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 14, 2025):

@nathanjcollins If you don't mind, could you also run the following from inside the Immich LXC:

cat /etc/apt/sources.list

cat /etc/apt/sources.list.d/immich.list

cat /etc/apt/preferences.d/immich

@vhsdream commented on GitHub (Aug 14, 2025): @nathanjcollins If you don't mind, could you also run the following from inside the Immich LXC: `cat /etc/apt/sources.list` `cat /etc/apt/sources.list.d/immich.list` `cat /etc/apt/preferences.d/immich`

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@deltamikealpha commented on GitHub (Aug 14, 2025):

Having the same issue - it's purely an on startup issue, I'd hazard a guess that if you've ever restarted it before you'll be OK - I was playing with converting an immich-in-lxc install to yours as it seems better supported.

@vhsdream whilst you directed at someone else, given i have the same and am writing at the same time. I've just spun this up as a new container.

cat /etc/apt/sources.list
root@immichtest:~# cat /etc/apt/sources.list
deb http://deb.debian.org/debian bookworm main contrib

deb http://deb.debian.org/debian bookworm-updates main contrib

deb http://security.debian.org bookworm-security main contrib

cat /etc/apt/sources.list.d/immich.list
root@immichtest:~# cat /etc/apt/sources.list.d/immich.list
deb http://deb.debian.org/debian testing main contrib

cat /etc/apt/preferences.d/immich
root@immichtest:~# cat /etc/apt/preferences.d/immich
Package: *
Pin: release a=testing
Pin-Priority: -10

cat /etc/issue
root@immichtest:~# cat /etc/issue
Debian GNU/Linux forky/sid \n \l

cat /etc/os-release
root@immichtest:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux forky/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=forky
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
VERSION_ID=12

@deltamikealpha commented on GitHub (Aug 14, 2025): Having the same issue - it's purely an on startup issue, I'd hazard a guess that if you've ever restarted it before you'll be OK - I was playing with converting an immich-in-lxc install to yours as it seems better supported. @vhsdream whilst you directed at someone else, given i have the same and am writing at the same time. I've just spun this up as a new container. `cat /etc/apt/sources.list` root@immichtest:~# cat /etc/apt/sources.list deb http://deb.debian.org/debian bookworm main contrib deb http://deb.debian.org/debian bookworm-updates main contrib deb http://security.debian.org bookworm-security main contrib `cat /etc/apt/sources.list.d/immich.list` root@immichtest:~# cat /etc/apt/sources.list.d/immich.list deb http://deb.debian.org/debian testing main contrib `cat /etc/apt/preferences.d/immich` root@immichtest:~# cat /etc/apt/preferences.d/immich Package: * Pin: release a=testing Pin-Priority: -10 `cat /etc/issue` root@immichtest:~# cat /etc/issue Debian GNU/Linux forky/sid \n \l `cat /etc/os-release` root@immichtest:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux forky/sid" NAME="Debian GNU/Linux" VERSION_CODENAME=forky ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" VERSION_ID=12

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@nathanjcollins commented on GitHub (Aug 14, 2025):

@nathanjcollins If you don't mind, could you also run the following from inside the Immich LXC:

cat /etc/apt/sources.list

cat /etc/apt/sources.list.d/immich.list

cat /etc/apt/preferences.d/immich

root@immich:~# cat /etc/apt/sources.list
deb http://deb.debian.org/debian bookworm main contrib

deb http://deb.debian.org/debian bookworm-updates main contrib

deb http://security.debian.org bookworm-security main contrib

root@immich:# cat /etc/apt/sources.list.d/immich.list
deb http://deb.debian.org/debian testing main contrib
root@immich:# cat /etc/apt/preferences.d/immich
Package: *
Pin: release a=testing
Pin-Priority: -10
root@immich:~#

Sorry I had actually deleted the LXC and had to recreate it

@nathanjcollins commented on GitHub (Aug 14, 2025): > [@nathanjcollins](https://github.com/nathanjcollins) If you don't mind, could you also run the following from inside the Immich LXC: > > `cat /etc/apt/sources.list` > > `cat /etc/apt/sources.list.d/immich.list` > > `cat /etc/apt/preferences.d/immich` root@immich:~# cat /etc/apt/sources.list deb http://deb.debian.org/debian bookworm main contrib deb http://deb.debian.org/debian bookworm-updates main contrib deb http://security.debian.org bookworm-security main contrib root@immich:~# cat /etc/apt/sources.list.d/immich.list deb http://deb.debian.org/debian testing main contrib root@immich:~# cat /etc/apt/preferences.d/immich Package: * Pin: release a=testing Pin-Priority: -10 root@immich:~# Sorry I had actually deleted the LXC and had to recreate it

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 14, 2025):

Thanks, that helps some. I had a feeling it was going to get dicey with PVE9/Debian 13, but I have limited testing capability in that regard.

@nathanjcollins @deltamikealpha can you both confirm this for me: This only happens when you install it on PVE9, and not PVE8? @nathanjcollins you seemed to have mentioned this happened on 8 but I ran a fresh install of Immich just yesterday and it can start and reboot just fine.

@vhsdream commented on GitHub (Aug 14, 2025): Thanks, that helps some. I had a feeling it was going to get dicey with PVE9/Debian 13, but I have limited testing capability in that regard. @nathanjcollins @deltamikealpha can you both confirm this for me: This only happens when you install it on PVE9, and not PVE8? @nathanjcollins you seemed to have mentioned this happened on 8 but I ran a fresh install of Immich just yesterday and it can start and reboot just fine.

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@nathanjcollins commented on GitHub (Aug 14, 2025):

Thanks, that helps some. I had a feeling it was going to get dicey with PVE9/Debian 13, but I have limited testing capability in that regard.

@nathanjcollins @deltamikealpha can you both confirm this for me: This only happens when you install it on PVE9, and not PVE8? @nathanjcollins you seemed to have mentioned this happened on 8 but I ran a fresh install of Immich just yesterday and it can start and reboot just fine.

I'm pretty sure it happened on PVE8, but I cannot confirm as I've lost all logs and I've updated. If I get some time tomorrow I might just re-install PVE8 and give it a go there. I think the only reason I updated to PVE9 is because I ran into this issue.

@nathanjcollins commented on GitHub (Aug 14, 2025): > Thanks, that helps some. I had a feeling it was going to get dicey with PVE9/Debian 13, but I have limited testing capability in that regard. > > [@nathanjcollins](https://github.com/nathanjcollins) [@deltamikealpha](https://github.com/deltamikealpha) can you both confirm this for me: This only happens when you install it on PVE9, and not PVE8? [@nathanjcollins](https://github.com/nathanjcollins) you seemed to have mentioned this happened on 8 but I ran a fresh install of Immich just yesterday and it can start and reboot just fine. I'm pretty sure it happened on PVE8, but I cannot confirm as I've lost all logs and I've updated. If I get some time tomorrow I might just re-install PVE8 and give it a go there. I think the only reason I updated to PVE9 is because I ran into this issue.

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@deltamikealpha commented on GitHub (Aug 14, 2025):

@vhsdream I can't confirm with PVE8 - I didn't try, but it's happened each time today on PVE9.

@deltamikealpha commented on GitHub (Aug 14, 2025): @vhsdream I can't confirm with PVE8 - I didn't try, but it's happened each time today on PVE9.

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@Mithias-uk commented on GitHub (Aug 14, 2025):

I'm on PVE 8.4 and its happened on mine. Not sure if helpful, but mine is set to Debian 12 and if I run 8to9 on the host I get this:-

FAIL: systemd-boot meta-package installed. This will cause problems on upgrades of other boot-related packages. Remove 'systemd-boot' See https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#sd-boot-warning for more information.

If I get a chance later I'll try remove systemd-boot (as its suggest in that link its safe to do so if highlighted in the checks) and see if that makes a difference

@Mithias-uk commented on GitHub (Aug 14, 2025): I'm on PVE 8.4 and its happened on mine. Not sure if helpful, but mine is set to Debian 12 and if I run 8to9 on the host I get this:- FAIL: systemd-boot meta-package installed. This will cause problems on upgrades of other boot-related packages. Remove 'systemd-boot' See https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#sd-boot-warning for more information. If I get a chance later I'll try remove systemd-boot (as its suggest in that link its safe to do so if highlighted in the checks) and see if that makes a difference

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@Mithias-uk commented on GitHub (Aug 14, 2025):

Okay, so simply removing systemd-boot doesn't work (I expected it wouldn't as was just a package). We've got confirmation this also affects PVE9 right? Tempted to Yolo upto that later on this evening

@Mithias-uk commented on GitHub (Aug 14, 2025): Okay, so simply removing systemd-boot doesn't work (I expected it wouldn't as was just a package). We've got confirmation this also affects PVE9 right? Tempted to Yolo upto that later on this evening

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 14, 2025):

Yes I've also just confirmed it does happen on 8 - something must have changed just since yesterday! And of course it's annoying when I ask y'all to provide details from inside the LXC when it's not even able to start.

@vhsdream commented on GitHub (Aug 14, 2025): Yes I've also just confirmed it does happen on 8 - something must have changed just since yesterday! And of course it's annoying when I ask y'all to provide details from inside the LXC when it's not even able to start.

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@deltamikealpha commented on GitHub (Aug 14, 2025):

I've left the container running that I created before, if it's helpful to grab anything from it then I'm fine to do so - but if you can repro now that probably does help things!

@deltamikealpha commented on GitHub (Aug 14, 2025): I've left the container running that I created before, if it's helpful to grab anything from it then I'm fine to do so - but if you can repro now that probably does help things!

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@Bonfra04 commented on GitHub (Aug 14, 2025):

Hi there, just had the same issue. Just wanted to point out that this allowed me to boot into the container:

run on the host:

pct mount <ctid>
cat /etc/debian_version > /var/lib/lxc/<ctid>/rootfs/etc/debian_version
pct unmount <ctid>

I know its just a dirty fix and doesn't solve the actual problem but it may help investigate the issue as it renders the container bootable with ease

@Bonfra04 commented on GitHub (Aug 14, 2025): Hi there, just had the same issue. Just wanted to point out that this allowed me to boot into the container: run on the host: ``` pct mount <ctid> cat /etc/debian_version > /var/lib/lxc/<ctid>/rootfs/etc/debian_version pct unmount <ctid> ``` I know its just a dirty fix and doesn't solve the actual problem but it may help investigate the issue as it renders the container bootable with ease

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 14, 2025):

@Bonfra04 lol I was just about to post that workaround! Nah it fixes it as far as I'm concerned; we'll just have to remember that this was done.

Going to submit a quick PR for this.

@vhsdream commented on GitHub (Aug 14, 2025): @Bonfra04 lol I was just about to post that workaround! Nah it fixes it as far as I'm concerned; we'll just have to remember that this was done. Going to submit a quick PR for this.

kerem commented

2026-02-26 12:48:58 +03:00

Author

Owner

@Bonfra04 commented on GitHub (Aug 14, 2025):

XD if it works for you I'm all in. Till it works it works ¯_(ツ)_/¯
It just need to be held into account that the rest of the metadata isn't updated:

root@immich:~# cat /etc/issue
Debian GNU/Linux forky/sid \n \l

root@immich:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux forky/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=forky
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
VERSION_ID=12
root@immich:~# cat /etc/debian_version
12.11

but the pre-start scripts only check that file so win-win

@Bonfra04 commented on GitHub (Aug 14, 2025): XD if it works for you I'm all in. Till it works it works ¯\_(ツ)_/¯ It just need to be held into account that the rest of the metadata isn't updated: ``` root@immich:~# cat /etc/issue Debian GNU/Linux forky/sid \n \l root@immich:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux forky/sid" NAME="Debian GNU/Linux" VERSION_CODENAME=forky ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" VERSION_ID=12 root@immich:~# cat /etc/debian_version 12.11 ``` but the pre-start scripts only check that file so win-win

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 14, 2025):

@Bonfra04 The VERSION_ID=12 even had to be added way back at the beginning otherwise the install script would fail. So it's a bit of a patchwork for sure.

And using 13.0 as the version seems to work for my LXC on Proxmox 8.4, so I chose that in the PR because I assume it'll work for Proxmox 9.

@vhsdream commented on GitHub (Aug 14, 2025): @Bonfra04 The `VERSION_ID=12` even had to be added way back at the beginning otherwise the install script would fail. So it's a bit of a patchwork for sure. And using 13.0 as the version seems to work for my LXC on Proxmox 8.4, so I chose that in the PR because I assume it'll work for Proxmox 9.

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 14, 2025):

Anyone out there who is on PVE9 feel like doing a fresh Immich install to super-confirm the fix is working?

@vhsdream commented on GitHub (Aug 14, 2025): Anyone out there who is on PVE9 feel like doing a fresh Immich install to super-confirm the fix is working?

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@lukalaza commented on GitHub (Aug 14, 2025):

Using PVE 8.4 I am getting an error during install:

Created user, env file, scripts and services
sed: -e expression #1, char 9: unterminated `s' command

[ERROR] in line 459: exit code 0: while executing command sed -i 's/.*/13.0' /etc/debian_version

[ERROR] in line 1353: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

@lukalaza commented on GitHub (Aug 14, 2025): Using PVE 8.4 I am getting an error during install: ``` Created user, env file, scripts and services sed: -e expression #1, char 9: unterminated `s' command [ERROR] in line 459: exit code 0: while executing command sed -i 's/.*/13.0' /etc/debian_version [ERROR] in line 1353: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)" ```

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@nathanjcollins commented on GitHub (Aug 14, 2025):

Using PVE 8.4 I am getting an error during install:

Created user, env file, scripts and services
sed: -e expression #1, char 9: unterminated `s' command

[ERROR] in line 459: exit code 0: while executing command sed -i 's/.*/13.0' /etc/debian_version

[ERROR] in line 1353: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

Same issue for me on PVE 9

@nathanjcollins commented on GitHub (Aug 14, 2025): > Using PVE 8.4 I am getting an error during install: > > ``` > Created user, env file, scripts and services > sed: -e expression #1, char 9: unterminated `s' command > > [ERROR] in line 459: exit code 0: while executing command sed -i 's/.*/13.0' /etc/debian_version > > [ERROR] in line 1353: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)" > ``` Same issue for me on PVE 9

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 14, 2025):

The damn forward slash. OK please try again at your leisure (since Immich takes so long to install).

@vhsdream commented on GitHub (Aug 14, 2025): The damn forward slash. OK please try again at your leisure (since Immich takes so long to install).

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@nathanjcollins commented on GitHub (Aug 15, 2025):

The damn forward slash. OK please try again at your leisure (since Immich takes so long to install).

I can confirm a fresh install on PVE 9.0.5 works, thank you!

@nathanjcollins commented on GitHub (Aug 15, 2025): > The damn forward slash. OK please try again at your leisure (since Immich takes so long to install). I can confirm a fresh install on PVE 9.0.5 works, thank you!

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@FutureCow commented on GitHub (Aug 15, 2025):

@vhsdream where do you use the /etc/apt/sources.d/immich.list for?
The testing repo in this files changed of course from trixie to forky after the release of trixie. So when you update a testing release, the update will push trixie (old testing) to forky (new testing). You can change the immich.list to trixie instead of testing?(or i'm missing the point here)

E: Repository 'http://deb.debian.org/debian testing InRelease' changed its 'Codename' value from 'trixie' to 'forky'

@FutureCow commented on GitHub (Aug 15, 2025): @vhsdream where do you use the /etc/apt/sources.d/immich.list for? The testing repo in this files changed of course from trixie to forky after the release of trixie. So when you update a testing release, the update will push trixie (old testing) to forky (new testing). You can change the immich.list to trixie instead of testing?(or i'm missing the point here) `E: Repository 'http://deb.debian.org/debian testing InRelease' changed its 'Codename' value from 'trixie' to 'forky'`

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@Mithias-uk commented on GitHub (Aug 15, 2025):

Updated my PVE to 9 last night and tried fresh install of Immich this morning. It now installs fine, and reboots fine, but it appears Immich isn't available on :2283 like before. I'm trying to find out now if its listening somewhere else instead or if its something with the install but any ideas?

@Mithias-uk commented on GitHub (Aug 15, 2025): Updated my PVE to 9 last night and tried fresh install of Immich this morning. It now installs fine, and reboots fine, but it appears Immich isn't available on :2283 like before. I'm trying to find out now if its listening somewhere else instead or if its something with the install but any ideas?

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@lukalaza commented on GitHub (Aug 15, 2025):

I can confirm that the same thing is happening to me, it's not available on :2283. It's also not listening anywhere else as far as I saw, I deleted the LXC so I am unable to confirm that at this moment

@lukalaza commented on GitHub (Aug 15, 2025): I can confirm that the same thing is happening to me, it's not available on :2283. It's also not listening anywhere else as far as I saw, I deleted the LXC so I am unable to confirm that at this moment

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@torrvick commented on GitHub (Aug 15, 2025):

@lukalaza @Mithias-uk if you look in /var/log/immich/web.log, you will see an error with VectorChord because their new version was released today, which is incompatible with immich. So I rolled back to VectorChord 0.4.3 https://github.com/tensorchord/VectorChord/releases/tag/0.4.3, then the steps from here: https://immich.app/docs/administration/postgres-standalone/#updating-vectorchord And everything works now

@torrvick commented on GitHub (Aug 15, 2025): @lukalaza @Mithias-uk if you look in /var/log/immich/web.log, you will see an error with VectorChord because their new version was released today, which is incompatible with immich. So I rolled back to VectorChord 0.4.3 https://github.com/tensorchord/VectorChord/releases/tag/0.4.3, then the steps from here: https://immich.app/docs/administration/postgres-standalone/#updating-vectorchord And everything works now

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@Mithias-uk commented on GitHub (Aug 15, 2025):

Is it possible to get updated in the script? I'll then test deployment.

@torrvick have you got the steps you used for this? Debian isn't my first language so I'm struggling getting all the steps together, mostly around which package in apt

@Mithias-uk commented on GitHub (Aug 15, 2025): Is it possible to get updated in the script? I'll then test deployment. @torrvick have you got the steps you used for this? Debian isn't my first language so I'm struggling getting all the steps together, mostly around which package in apt

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@vhsdream commented on GitHub (Aug 15, 2025):

When it rains it pours.

@vhsdream commented on GitHub (Aug 15, 2025): When it rains it pours.

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@torrvick commented on GitHub (Aug 15, 2025):

@Mithias-uk Sure)

wget https://github.com/tensorchord/VectorChord/releases/download/0.4.3/postgresql-16-vchord_0.4.3-1_amd64.deb (or change to you architecture if it's not amd64)
apt install ./postgresql-16-vchord_0.4.3-1_amd64.deb
get you pass here: cat /opt/immich/.env
psql -h 127.0.0.1 -U immich -d immich and paste your pass from above
do this https://immich.app/docs/administration/postgres-standalone/#updating-vectorchord
that's all

@torrvick commented on GitHub (Aug 15, 2025): @Mithias-uk Sure) 1. wget https://github.com/tensorchord/VectorChord/releases/download/0.4.3/postgresql-16-vchord_0.4.3-1_amd64.deb (or change to you architecture if it's not amd64) 2. apt install ./postgresql-16-vchord_0.4.3-1_amd64.deb 3. get you pass here: cat /opt/immich/.env 4. psql -h 127.0.0.1 -U immich -d immich and paste your pass from above 5. do this https://immich.app/docs/administration/postgres-standalone/#updating-vectorchord that's all

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@Mithias-uk commented on GitHub (Aug 15, 2025):

Confirmed that works :-) Since it's a fresh install, I'll remove and await for the fixes to be rolled into the deployment script. Thanks @torrvick and @vhsdream for your work! And I haven't said it before but thanks @tteck for everything you did, made learning a bit of Linux and Proxmox for primary a Windows admin person possible here

@Mithias-uk commented on GitHub (Aug 15, 2025): Confirmed that works :-) Since it's a fresh install, I'll remove and await for the fixes to be rolled into the deployment script. Thanks @torrvick and @vhsdream for your work! And I haven't said it before but thanks @tteck for everything you did, made learning a bit of Linux and Proxmox for primary a Windows admin person possible here

kerem commented

2026-02-26 12:48:59 +03:00

Author

Owner

@Mithias-uk commented on GitHub (Aug 15, 2025):

Deployed, customised and rebooted and she still lives! Thanks all!

@Mithias-uk commented on GitHub (Aug 15, 2025): Deployed, customised and rebooted and she still lives! Thanks all!

kerem referenced this issue

2026-02-26 13:32:41 +03:00

[PR #1457] [MERGED] [Github Action] Update CHANGELOG.md #3183

Rows
Columns

[GH-ISSUE #6836] Immich unsupported debian version '14' #1457

✅ Have you read and understood the above guidelines?

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

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

⚙️ What settings are you using?

🖥️ Which Linux distribution are you using?

📝 Provide a clear and concise description of the issue.

🔄 Steps to reproduce the issue.

❌ Paste the full error output (if available).

🖼️ Additional context (optional).