Update to v1.138
Hallo,
I tried updating to v1.138. Proxmox v9. Immich in LCX Container, installed with https://community-scripts.github.io/ProxmoxVE/scripts?id=immich
Immich
v1.137.3
ExifTool
13.00
Node.js
v22.18.0
Libvips
8.17.1
I wanted to update to v1.138 and entered the installation link bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)" in the console in the container, and the update worked, except for:
: Reading changelogs... (Reading database ... 44839 files and directories currently installed.) Preparing to unpack /opt/staging/vchord.deb ... Unpacking postgresql-16-vchord (0.5.0-1) over (0.4.3-1) ... Setting up postgresql-16-vchord (0.5.0-1) ... Processing triggers for postgresql-common (281.pgdg120+1) ... Building PostgreSQL dictionaries from installed myspell/hunspell packages... Removing obsolete dictionary files: ERROR: could not find function "_vchordg_support_halfvec_cosine_ops_wrapper" in file "/usr/lib/postgresql/16/lib/vchord.so" [ERROR] in line 91: exit code 0: while executing command $STD sudo -u postgres psql -d immich -c "ALTER EXTENSION vchord UPDATE;" root@Immich:~#
I've restored the first backup I made after installing Immich. I get the same error when I try to update.
My home server is still under construction. Oh yeah, I'm a noob... But I like Immich.
I'm wondering: Is this a bug in community scripts and i ask in https://github.com/community-scripts/ProxmoxVE/discussions
10 Replies
:wave: Hey @Rantanplaq,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.This looks very much like an issue with the community script. I'd ask them first
Also, we discourage the usage of that script
hm okay. I'm still, or again, at the beginning. ty
sry, a stupid question : Which way is right for Immich and Proxmox in LCX Container?
Docker and Portainer in a LCX Container?
Technically docker is discouraged by us and proxmox in an lxc.
But if it's lesser of two evils, I would choose the docker install in an LXC over the helper scripts. More control and insight into what's going on.
The right way FWIW is a VM
hm yes yes, i understand... 😄 Ty for answer, very friendly.
Maybe I HAVE to ask again later.. :x
Maybe I HAVE to ask again later.. :xI doubt the answer to this is gonna change on our end :P
TL;DR they did an unfortunate step of the an incompatible container