When starting both containers simultaneously, there is a race condition when the monerod container didn't create the lmbd folder yet, but the explore container tries to access it. It obviously exits with an error. (While I ran into this error, I didn't reproduced it yet).
While initial sync, the explore container uses a lot of CPU, leaving less resources to monerod. Because of that, I think it is a great idea to delay the start of explore and wait until sync finishes.
On the other hand, I had some issues on limited RAM servers when explore wasn't started first. Actually, even with the current compose setup, it hang up without any message, and when I restarted only explore container, it exited with code 137 (likely a RAM issue). Now if this is because of the initial sync, then there is another reason to delay the container, I'll test it again after sync finished.
Delaying the start of the
explorecontainer during the initial blockchain sync would be beneficial toWhen starting both containers simultaneously, there is a race condition when the
monerodcontainer didn't create the lmbd folder yet, but theexplorecontainer tries to access it. It obviously exits with an error. (While I ran into this error, I didn't reproduced it yet).While initial sync, the
explorecontainer uses a lot of CPU, leaving less resources tomonerod. Because of that, I think it is a great idea to delay the start ofexploreand wait until sync finishes.On the other hand, I had some issues on limited RAM servers when
explorewasn't started first. Actually, even with the current compose setup, it hang up without any message, and when I restarted onlyexplorecontainer, it exited with code 137 (likely a RAM issue). Now if this is because of the initial sync, then there is another reason to delay the container, I'll test it again after sync finished.