Issue 135: a container's mesh names are not compared #165

2026-09-28T15:19:36Z

mesh-admin commented

2026-09-28 15:19:36 +00:00

No description provided.

mesh-admin added 1 commit 2026-09-28 15:19:36 +00:00

Issue 135: a container's mesh names are not compared, so a moved address is never noticed 4789624857

One container restarted 2286 times over five days while the mesh reported the machine as doing what it
was told. Its overlay address was five days out of date: the host compares a container by a digest of
its spec, and the mesh's names were not in it, so a container whose image and files never changed was
left alone holding a name that no longer resolved. Forty-eight others were current only because
something else had recreated them.

The same fault as issue 045, in the field that was left out. Resolved by putting the names in the
digest.

mesh-admin merged commit d6b62387f2 into main

2026-09-28 15:19:37 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#165