abra continues deployment when the image doesn't exist on the registry #865

New Issue

fauno · 2026-06-10T17:34:40Z

fauno commented

2026-06-10 17:34:40 +00:00

i keep getting this warning when upgrading kimai, first because they changed the tag format, and now because i was upgrading before the image was pushed. last time i forgot about it assuming it would fail at some point, but it kept going for a number of hours until i ^c it. is this expected?

WARN image kimai/kimai2:2.60.0 could not be accessed on a registry to record
its digest. Each node will access kimai/kimai2:2.60.0 independently,
possibly leading to different nodes running different
versions of the image.

i keep getting this warning when upgrading kimai, first because they changed the tag format, and now because i was upgrading before the image was pushed. last time i forgot about it assuming it would fail at some point, but it kept going for a number of hours until i ^c it. is this expected? ``` WARN image kimai/kimai2:2.60.0 could not be accessed on a registry to record its digest. Each node will access kimai/kimai2:2.60.0 independently, possibly leading to different nodes running different versions of the image. ```

👀 1

fauno commented

2026-06-10 18:18:41 +00:00

i don't have this warning when i pull an image manually on the server that doesn't exist on the registry (ie because i tagged it myself), it works ok

decentral1se added the

bug

label 2026-06-11 10:50:40 +00:00

Sign in to join this conversation.