Closed ahasna closed 1 month ago
Example of the errors:
nitro-testnode-sequencer-1 | WARN [07-10|11:55:57.392] coordinator failed finding sequencer wanting lockout err="sequencer priorities unset"
nitro-testnode-staker-unsafe-1 | WARN [07-10|11:55:57.682] validator address isn't whitelisted address=nil txSender=0x6A568afe0f82d34759347bb36F14A6bB171d2CBe
nitro-testnode-sequencer-1 | WARN [07-10|11:56:00.394] coordinator failed finding sequencer wanting lockout err="sequencer priorities unset"
nitro-testnode-sequencer-1 | WARN [07-10|11:56:03.400] coordinator failed finding sequencer wanting lockout err="sequencer priorities unset"
nitro-testnode-sequencer-1 | WARN [07-10|11:56:06.400] coordinator failed finding sequencer wanting lockout err="sequencer priorities unset"
Hello! Sorry for the very long delay. We've just updated nitro-testnode to by default use "simple-mode". In this mode, there is only one l2node present which does sequencing, batch posting, and staking. This should allow stopping with "docker-compose stop" and restarting with either docker-compose or testnode bash.
Hey! I am trying to setup a Arbitrum testnet environment in CI. Ai was able to follow the README and get things going locally and deploy some contracts of both L1 and L2 successfully. However, when I attempt to "freeze" my setup, by executing
docker commit
to make it easier and faster to transfer to other devs, I start hitting all sorts of errors.Is there a way to make the setup time faster and/or preserving some initial state for running a local network?