Nodes started with docker run keep their identity when recreated
Only our Compose file kept a Docker node's machine ID, so a node started with docker run or a hand-written Compose file could come back as a new node. From v0.0.113 the image keeps the ID on its /data volume itself.
A node’s identity on the network comes from its machine ID, which the edge node image doesn’t ship with. Our Compose file supplied one and kept it on a volume, but a node started with plain docker run, or with a Compose file of your own, had no such volume. Recreating the container, for example to update the image, could bring it back as a brand new node: Active Node Hours back to zero, and its leaderboard place, badges and history gone.
From v0.0.113 the image looks after this itself. When it starts, it creates a machine ID if there isn’t one and keeps a copy on the /data volume, and it restores that copy whenever the container is recreated.
What you need to do
- Pull v0.0.113 or later, and keep your
/datavolume. That’s where the ID now lives, alongside the node’s other data. - Using our Compose file: nothing. An ID already on its identity volume is kept and copied to
/data. - A node that already keeps its own ID: nothing. Since v0.0.104, a node with no machine ID creates one of its own, and that ID keeps taking priority, so updating doesn’t make it pair again.