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

Merged
mesh-admin merged 1 commits from issue/135-a-containers-mesh-names into main 2026-09-28 15:19:37 +00:00
1 Commits
Author SHA1 Message Date
jschoubben 4789624857 Issue 135: a container's mesh names are not compared, so a moved address is never noticed
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.
2026-09-28 17:19:35 +02:00