Image update process
Is a simple `incus-compose up --recreate` (essentially down and up) supposed to be enough to handle updating images? It seems that this causes an error due to the two image stores being out of sync.
`incus-compose down` doesn't seem to remove images from the active project, only instances. Here are the remaining images on the project.
```bash
% incus image list -c lfdu
+------------------------------------------+--------------+-----------------------------------------+-----------------------+
| ALIAS | FINGERPRINT | DESCRIPTION | UPLOAD DATE |
+------------------------------------------+--------------+-----------------------------------------+-----------------------+
| ghcr.io/pouzor/homelable-backend:latest | b5c816153395 | ghcr.io/pouzor/homelable-backend (OCI) | 2026/05/16 13:25 EEST |
+------------------------------------------+--------------+-----------------------------------------+-----------------------+
| ghcr.io/pouzor/homelable-frontend:latest | 95fdeb083178 | ghcr.io/pouzor/homelable-frontend (OCI) | 2026/05/16 13:25 EEST |
+------------------------------------------+--------------+-----------------------------------------+-----------------------+
```
and here are the new images that were auto-updated by Incus, in the incus-compose-images project.
```bash
% incus image list -c lfdu ghcr.io/pouzor/homelable-
+------------------------------------------+--------------+-----------------------------------------+-----------------------+
| ALIAS | FINGERPRINT | DESCRIPTION | UPLOAD DATE |
+------------------------------------------+--------------+-----------------------------------------+-----------------------+
| ghcr.io/pouzor/homelable-backend:latest | 5ac81ea00d2a | ghcr.io/pouzor/homelable-backend (OCI) | 2026/05/16 21:31 EEST |
+------------------------------------------+--------------+-----------------------------------------+-----------------------+
| ghcr.io/pouzor/homelable-frontend:latest | e4e0d9fe225b | ghcr.io/pouzor/homelable-frontend (OCI) | 2026/05/16 21:32 EEST |
+------------------------------------------+--------------+-----------------------------------------+-----------------------+
```
Error when trying to bring up containers in this state.
```bash
% incus-compose up --debug
03:10 DBG Using connection remote=local
03:10 DBG Got project url=http://unix.socket name=incus-compose-images incus_name=incus-compose-images
03:10 DBG Got project url=http://unix.socket name=homelable incus_name=homelable
03:10 DBG Getting image url=http://unix.socket project=homelable incus_project=homelable image=ghcr.io/pouzor/homelable-backend:latest service=backend
03:10 DBG Getting image url=http://unix.socket project=homelable incus_project=homelable image=ghcr.io/pouzor/homelable-frontend:latest service=frontend
03:10 DBG network:homelable
03:10 DBG Ensure url=http://unix.socket project=homelable incus_project=homelable resources="[network(ic-3wro4vun5q) instance(backend-1) instance(frontend-1) image(ghcr.io/pouzor/homelable-backend:latest) image(ghcr.io/pouzor/homelable-frontend:latest)]"
03:10 ERR Creating resources url=http://unix.socket project=homelable incus_project=homelable error="resource not found getting image: instance(backend-1): Image \"5ac81ea00d2a8efbe02992e3400e7b49f458d1ef7a659356d0a5c5bea63381e8\" not found\nresource not found getting image: instance(frontend-1): Image \"e4e0d9fe225b28d65199d8157738b0dc29df761f0cd212cb25c84b152db4ceaa\" not found"
```
`incus-compose down --project` wipes the whole project including the images. This works but seems more destructive than necessary to pull in the new images.
incus 7.0.0
issue