You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When installing a new fresh node 13.1 on a new Ubuntu 22.04 server with docker configured as non root,
git clone https://github.com/Cardinal-Cryptography/aleph-node-runner
cd aleph-node-runner
You get the directory and script run_node.sh that will configure the node using the file in validator_testnet
For any reason, if you Ctrl+C during the snapshot phase, the script will not perform well at the end (I tried it twice and each time you end it with a restarting container)
For any reason, if you didn't correctly configure the env/validator_testnet BEFORE launching the script, the container will not be corrected. Example to reproduce:
start the run_node.sh script until the end
modify ports in the env/validator_testnet
docker stop container
start the run_node.sh script again
You will get a container without the ports you changed. I tried this twice also.
In my case, I wrote "for any reason", to me the reason was that I was using a ssh session, I made the script via the ssh session whereas I wanted to start it directly from the server itself, so I Ctrl+C in the middle of the script from ssh before relaunching it directly on the server.
The text was updated successfully, but these errors were encountered:
When installing a new fresh node 13.1 on a new Ubuntu 22.04 server with docker configured as non root,
You get the directory and script
run_node.sh
that will configure the node using the file in validator_testnetenv/validator_testnet
BEFORE launching the script, the container will not be corrected. Example to reproduce:run_node.sh
script until the endenv/validator_testnet
docker stop
containerrun_node.sh
script againIn my case, I wrote "for any reason", to me the reason was that I was using a ssh session, I made the script via the ssh session whereas I wanted to start it directly from the server itself, so I Ctrl+C in the middle of the script from ssh before relaunching it directly on the server.
The text was updated successfully, but these errors were encountered: