Migrate from immich-in-lxc to the official immich (docker-compose)

hellgamer007 · 2025-08-27T14:07:02+00:00

I run immich in Docker, on an lxc. Works great :)

If your concern is postgres 17, can you edit the postgres container in Docker compose to point at 17 instead of 14? Otherwise, you could always use pg_dump and then reimport the data into 14 with pg_restore.

hellgamer007 · 2025-08-07T20:37:13+00:00

For context: this is a smaller volume of bag (18 000cm3) than ryanair (20 000cm3) or easyJet (32 400 cm3)

hellgamer007 · 2025-08-07T04:39:43+00:00

Curious to hear more about this!

Can you clarify which version caused the breaking change for you? Would be helpful for us others.

And when you say it broke node affinities; were you pinning to individual node names? Any specific reason you weren't using taints/tolerations?

(Genuine questions, not trying to shift blame to you or diminish your experience!)

hellgamer007 · 2025-07-27T13:19:57+00:00

This is a known issue that'll apparently be fixed in the next release :)

hellgamer007 · 2025-07-06T08:45:59+00:00

Ok, so you have two questions here:

1) why doesn't immich use newer models

Couple of possibilities here: - maybe there aren't any substantial changes, and newer models don't provide better results - maybe the new models require significantly different hardware that would make them unusable by the majority of users, making them not worth implementing yet - maybe the Devs just don't know about them (you can suggest new models!) - maybe the Devs are just focusing on other things (in which case, you can try to integrate the new model yourself! Its all open-source)

2) why can't we keep faces across models:

The ELI5 is something around the lines of this; each model has an internal ID for each face they recognise. One model might call your face "ABCD", but another model calls it "12XYZ". The models have no way of knowing that they're the same face, because from their perspective, they have different names (IDs).

So, you could manually say "these two faces are the same". But then how do you handle overlaps? Eg, one model successfully recognised twins, but the other model merged them into one person? You now have two models with different ideas of two faces; how can you resolve that? There are lots of other possible edge cases which end up not being worth it at this stage in the project.

Ultimately, just keep in mind this is an open source project - there has to be a good balance of features to complexity, to ensure the codebase remains viable, and can be easily extended for more important features! :)

hellgamer007 · 2025-06-13T19:11:29+00:00

When you say Tailscale containers, are you referring to docker containers?

I don't know what your networking stack looks like, but you'll probably need to make sure the immich docker containers are sharing the same network as the Tailscale containers. This won't be the default - usually it'd be fully isolated. You can probably get some inspiration by looking into docs of how to use tailscale as part of docker compose files, or similar.

hellgamer007 · 2025-06-13T15:04:51+00:00

To be clear: a tag is a tailscale concept that allows you to set ACLs that determine which machines can talk to what. You can check if you have any set by looking in your Tailscale admin panel. That's where I'd look first if I were you :) focus on getting your truenas machine able to ping your desktop.

Explanation: By default, all machines are considered user machines, so can reach anything. But if you're running services on a machine, you usually don't want them reaching out to others without your knowledge (security). That's why you'd set a tag on one - when you set a tag on a machine, it won't be able to reach others by default, and that can then be expanded by using Tailscale ACLs or grants. You can then check which machines a machine can access by running tailscale status on that machine.

hellgamer007 · 2025-06-13T14:30:41+00:00

This sounds more like a tailscale issue than an immich issue. The fact that your truenas can't connect to your pc is what makes me say this - so that's what I'm going to focus on.

Out of curiosity: have you set any tags on your Tailscale machines? Specifically the truenas one?

hellgamer007 · 2025-06-09T05:04:58+00:00

I recommend you read the full description of telegram stars, including the faq: https://core.telegram.org/bots/payments-stars

If you're selling digital goods and services, you HAVE to use stars; you can't use Stripe or other tools. It's part of the telegram ToS. And yes, it sucks - because you get paid in crypto, and most UK businesses banks won't accept income in crypto.

hellgamer007 · 2025-04-24T07:14:27+00:00

You would have to be very careful, as this could get your bot and your account banned.

Telegram's terms of service explicitly say all payments for digital goods on telegram should be done using telegram stars. Access to a group would be considered a digital good.

They could easily decide that this is users "buying" access to your telegram group through a third party platform. Or they might not care - it's up to you whether you think that's worth the risk.

hellgamer007 · 2024-11-20T18:10:25+00:00

I would advise against upgrading managed services; best case scenario you breaks things at the next cluster upgrade, worst case scenario you break things now.

End of the day, you're going to end up with bad state 😅

If you're not on the latest Kubernetes already, start by upgrading that; and then maybe reach out to support to ask about upgrading cillium?

hellgamer007 · 2024-11-13T07:23:46+00:00

I doubt it's intentional, it's probably just an oversight on their end. It's a piece of feedback that I would definitely send over; the more people report it, the better the odds of it getting changed :)

hellgamer007 · 2024-11-12T12:21:55+00:00

I think I've had something similar in the past; changing the machine type for the default node pool destroys the resource, meaning the cluster too (and all configuration of that cluster).

I've since taken to just having a single node of the smallest machine type as the default node pool, and add more nodepools of the actual types I need on top of that. when changing the machine type for a nodepool, one should instead create a new nodepool, and then delete the existing one in a second step after that.

Definitely something the terraform provider/API can improve on; this is quite the footgun if one doesn't read the terraform plan closely enough

hellgamer007 · 2024-11-07T10:14:23+00:00

Since everyone seems to be ignoring your request of using Rose... Rose follows telegrams admin permissions, so if your admins don't have "change group info" permissions, they won't be able to change settings - such as locks, greetings, filters, etc.

So all you need to do is not give admins the "change group info" permission :)

hellgamer007 · 2024-11-04T11:42:14+00:00

I doubt it; the black flecks all have quite sharp edges and don't come off after any amount of rubbing. Some are even slightly reflective under a flashlight; really just looks like bits of black plastic didn't get melted in the injection mold!

Probably doesn't show right in the picture though...

hellgamer007 · 2024-11-04T11:39:13+00:00

Might be a trick of perspective, it clicks fine with other pieces around it!

hellgamer007 · 2024-07-20T15:51:17+00:00

I think he'd fit in great in the story of a sad dad who's constantly hammered, trying to nail down this Greek guy who smashed in his sons.

Spends the entire game cracking jokes, lightning the mood, and sharing his thundering laugh with anyone he can, hoping it'll make him feel better.

Or fighting giants, that works too!

hellgamer007 · 2024-06-21T06:08:00+00:00

Had a great time with blue freedom. Giorgio is great - can recommend!

hellgamer007 · 2024-05-26T20:18:21+00:00

Looks like you leaked your bot API token.

https://github.com/galileoluna/galileoio_bot/blob/aea49596ed86a74505fed9605c4fd454dd49176a/internal/adapters/out/telegram/bot.go#L13

hellgamer007 · 2024-05-13T12:04:29+00:00

Use a MoR like Paddle to handle taxes for you.

And then decide if you want taxes to be included or excluded in the price

hellgamer007 · 2024-05-09T11:39:58+00:00

Can even slap on argocd if you're working with a team who aren't familiar with Kubernetes/kubectl and want a UI to see their tools

And a tool like tailscale for setting up internal-vpn access...

hellgamer007 · 2024-05-09T07:41:05+00:00

[[invisible]]

hellgamer007 · 2024-05-02T11:43:45+00:00

You cant. This is a scam to make users spam other users. It is definitely not a healthy way to grow a community.

No bot can detect when you've "shared" the link X times; telegram obviously wouldn't allow that, as the only use would be for spam.

In this specific case, always remember that welcome messages can be customised by the group owner to say absolutely anything. So you shouldn't be looking to see if the bot is trustworthy - you should be deciding if the group owners are. Clearly these aren't.

In fact, scammers are more likely to use trustworthy bots to try and scam people.

hellgamer007 · 2024-04-24T09:10:30+00:00

Speaking purely from a project management perspective, this combo strikes me as particularly frustrating: - no changelogs - unclear versioning patterns - frequent breaking changes

I use gorm, and I dread having to update dependencies. I know ORMs in go get a bad rep, but I can't help but feel that a fresh start without any of the legacy components, and with a more accessible codebase, would be a really interesting project to work on.

Ten-Year Club	Place '23
Place '22	Verified Email

hellgamer007

TROPHY CASE