bug: restarting compose fails loading keystore

[strinnityk]

Problem

After running docker compose --compatibility up and all containers are healthily running; if restarted, nwaku containers won't boot properly. When restarted, these logs are output:

nwaku_2                   | ERR 2024-06-18 19:22:10.090+00:00 Mounting protocols failed                  tid=1 file=node_factory.nim:422 error="failed to mount waku RLN relay protocol: failed to mount WakuRlnRelay: could not initialize the group manager: the commitment does not have a membership"
nwaku_2                   | ERR 2024-06-18 19:22:10.090+00:00 Failed setting up node                     topics="wakunode main" tid=1 file=waku.nim:152 error="Mounting protocols failed: failed to mount waku RLN relay protocol: failed to mount WakuRlnRelay: could not initialize the group manager: the commitment does not have a membership"
nwaku_2                   | ERR 2024-06-18 19:22:10.090+00:00 Waku initialization failed                 topics="wakunode main" tid=1 file=wakunode2.nim:69 error="Failed setting up node: Mounting protocols failed: failed to mount waku RLN relay protocol: failed to mount WakuRlnRelay: could not initialize the group manager: the commitment does not have a membership"

Expected behavior

Restarted containers should generate a new keystore, or fetch from the existing keystore (if a volume were shared, which I believe it's currently not).

[stubbsta]

I don't see this locally when I stop the container and start it again. The existing keystore is used.
How are you restarting the containers? Are you restarting all containers or just the nwaku ones?

[strinnityk]

I don't see this locally when I stop the container and start it again. The existing keystore is used. How are you restarting the containers? Are you restarting all containers or just the nwaku ones?

I've just double checked, and it just happens when restarting the whole suite of containers. That is:

1. Running compose up
2. ctrl-c
3. Running compose up

If, while running compose, I stop and start only the nwaku containers, they do load their keystores and resume their activity normally.