Files
Nicolas De Loof df094b036c fix(images): tolerate containers whose image record is gone
A running container may reference an image record that no longer
exists: under the containerd image store, `up --build` with identical
content moves the tag to a new index digest (provenance attestation
churn) and the daemon drops the old index the container was created
from — without compose recreating the container, by design (#13636).
`docker rmi -f` of a running container's image produces the same state.

`compose images` used to fail the whole listing on the resulting
NotFound. Degrade to what the container itself knows (image ID, and
repository/tag when the reference is not a raw ID) instead of failing.

Fixes #14014

Signed-off-by: Nicolas De Loof <[email protected]>
2026-08-14 15:20:37 +02:00
..
2025-10-13 10:40:19 +02:00
2024-11-27 07:39:46 +01:00
2021-06-28 08:47:58 +02:00
2024-10-02 21:15:59 +02:00
2023-07-18 11:08:06 +02:00
2021-06-28 08:47:58 +02:00
2022-05-31 16:32:29 -05:00
2025-06-30 19:22:35 +02:00
2025-06-02 18:57:07 +02:00
2024-07-11 10:25:04 +02:00
2022-06-08 14:05:20 -05:00
2024-04-09 15:30:42 +02:00
2025-11-06 08:02:59 +01:00
2025-04-09 16:59:42 +02:00
2023-06-30 16:07:03 +02:00