neitsab
(Bastien Traverse)
May 29, 2026, 4:14pm
41
Yeah I was (and am still) hit by the same bug @kgoetz reported in Please use skopeo with --no-tags · Issue #3367 · lxc/incus · GitHub . Looking forward to a new release with it
I also went the manual route for Immich while hoping @jochumdev finds the time to add a configuration option for the pool name, as on IncusOS it’s local and not default.
If anyone is interested, I just published a detailed howto: Deploy Immich on IncusOS - Bastien Traverse
2 Likes
jochumdev
(René Jochum)
May 29, 2026, 7:10pm
42
I have a lot private stuff going on here. I think I get those bugfixes done by the end of June Mai .
Sorry.
EDIT: June → Mai
2 Likes
neitsab
(Bastien Traverse)
May 30, 2026, 12:24pm
43
Hey no worries @jochumdev , I hope my phrasing didn’t come across as passive-aggressive or something like that?
Please take all the time you need, you already did so much. I believe there should be 0 pressure or expectations in FOSS development work. I hope your matters will settle agreeably.
I’ve just opened Allow to configure storage pool name (#31) · Issues · René Jochum / incus-compose · GitLab to track the feature request, where I share my update of @Sagi ’s patch to apply cleanly on current HEAD and the error message I got after using it.
All the best
2 Likes
jochumdev
(René Jochum)
May 31, 2026, 7:17am
44
Thanks for asking! No, at all I just wanted to deliver.
This is what I’m working at, at the Moment (not Tech related): jochum.dev
Thank you! That makes it easier to track it down once I have to time to fix that and many thanks for looking for a fix!
Kind regards and all the best as well,
René
1 Like
jochumdev
(René Jochum)
May 31, 2026, 8:17am
45
3 Likes
jochumdev
(René Jochum)
May 31, 2026, 6:27pm
46
I got it working: test/fixtures/immich · main · René Jochum / incus-compose · GitLab needs the upcoming release or manual build.
It’s a quick and dirty fix, also I’m using unreliable image endpoints as well as one of my one uploads.
jochumdev
(René Jochum)
May 31, 2026, 11:37pm
47
pyrodogg:
In the case of Immich, the immich-server service is trying to access the database service at the network address “database”. This lookup fails because incus-compose starts the container as “database-1” and Incus appears to only provides a default DNS entry for the container name “database-1”.
For full compatibility, I think incus-compose would have to leverage Incus Network Zones and add DNS entries also for the service names in additional to the container names that get generated. This way the database service could be reached at either “database” or “database-1”. Docker supports both of these methods. I’ll leave links out for now.
One other feature request could help serve as a stopgap, If the “container_name” key were used, it could override the default container name generation and pin the name back to “database” instead of “database-1”. This is likely much easier to support than the deeper network integration.
I found the most straight forward way to solve this is for now:
$ incus network show .....
...
raw.dnsmasq: |
address=/web/10.222.209.52
address=/web/10.222.209.214
...
This will allow us to have both “web” and “web-X”.
Incus Network Zones require an authorative dns server and container_name doesn’t give anything sadly.
Thank you again @pyrodogg
EDIT: Done in
After instances start, RegisterScaleWatcher rewrites raw.dnsmasq on each managed bridge network with address=/{service}/{ip} entries. Both the service name (database) and instance name (database-1) resolve, with round-robin across scaled replicas....
1 Like
jochumdev
(René Jochum)
June 1, 2026, 2:02pm
49
1 Like