use packages for vaultwarden and immich?

[dionysius]

Hello dear Proxmox community,

I'm the maintainer of the debian packages for vaultwarden and immich. I wonder if you're interested in using those as source for your install scripts to make maintenance of the scripts easier - if at all. I can also see it to be fairly maintainable like it now if you always cross-check with their docker images. I also don't know if you overall prefer packages or always want to build by source. I'm using those services in an incus container (including hw-accelleration - i use the incus config gpu passthrough) so it should be reusable in your manual lxc container configs.

While vaultwarden is probably easy to use, immich comes with its own complexity regarding updated libraries and hw-accelleration. I currently provide updated libraries only when essentially necessary - I consider back-ported libraries to be either explicitly opt-in or provided bundled with a separate prefix. So most of those extra built libraries are still needed if you want the latest. The hw-acceleration part is easily configurable in the config file - given the drivers are installed beforehand and the device is passed to the container.

I just stumbled upon #8193 and thought this could be easier so I wanted to leave this suggestion.

At some point I may also tackle seafile-server since this is now docker only as well, but I have not yet a fleshed out plan.

[michelroegl-brunner]

@vhsdream you might want to look into that maybe

[vhsdream]

It's certainly something worth considering, since building Immich the way we do is so intensive and prone to mistakes on my part. This would vastly simplify things.

But there's also the subject of trust and transparency - simply adding a repo from an unknown and as-yet untrusted source presents it's own risks.

Still, I think we should not write this off completely.

@dionysius - checking the repo, it looks like you are using Vectorchord 1.0.0, which I don't think it supported by Immich yet. Have you noticed anything different, performance-wise?

[dionysius]

Trust and transparency is definitely a thing. I'm just a guy who was annoyed at a problem and created/started a solution. The source package is on github, the actions build it (signed with the key in the repo) which' source is also open. Previously I pushed the packages to packagecloud but since dionysius/vaultwarden-deb#20 I moved away from there. Every immich build is hundreds of MB. I did not find a suitable place to host the packages so https://github.com/dionysius/aarg was born and I now push the apt repository to cloudflare pages (repo signing keys linked on the apt page).

If you have a space to build and host the packages yourself, you could always pull/fork the repo and build it yourself as changes to the source is easily verified. But currently the packages are not perfect and I might have a slight different point of view of the expected result - so I think for you dionysius/immich-deb#8 is important to consider.

Regarding vectorchord 1.0.0 this just got recently bumped for immich 2.5.0+, also verified in their docs and they list it now as < 2.0 . I only use my build for a few weeks. The upgrade from 2.4 to 2.5 including the vectorchord 0.5 to 1.0 went seamless. The restart of immich-server took a little while to migrate, there's a log output noting the migration.

I can't say anything about the performance, since I don't know what is normal or fast, my files are loaded "cloud-based" with seafile-fuse, so only a subset of files is actually directly available. I was using the immich-distribution snap version before and was annoyed I couldn't configure hw-accel. That's how this whole project started.

I'm hoping that this project at some point gets collaboratively updated. But since it's so new this will take a little while. I found your project through an issue with openvino, where I found the fix with patchelf (is not needed anymore with 2.5.2 and it now wants python 3.13 for openvino)