status-go
status-go copied to clipboard
Multiple questions when starting a status node
Hi all and thanks for building Status!
Problem
I want to run a status node. For fun. This should be easy to do since we need nodes, right? In the process I encountered multiple problems/questions that could use better documentation in order to help me and others.
-
Docker tag: in the docs the tag 0.16.0 is fixed, which seems outdated. However, the list of alternative docker tags look very confusing to users. All the recent tags have some
-prerelease
suffix. The permanent tagslatest
/deploy-test
/deploy-beta
/deploy-postgres
/deploy-incent
/deploy-staging
are not documented. Could we have a tiny little guide in the dockerhub README helping to pick the right tag? -
Default command: Running
docker run --rm statusteam/status-go:0.16.0
(as documented here) results in the help message with a non-0 exit code. Even the help message shows a usage without arguments but the application does not like it. As soon as I add any of the suggested command line arguments, it works. - Ports: It is not documented which port I need to open in order for p2p connectivity to work
-
debug_metrics: How can I find docs to the
debug_metrics
RPC call? I did not find any on the web and the endpoint is not listed here. I had to find the required 1st parameter by trial and error and still don't understand what it means. - Peers 1: How can I find out if other peers can see me?
-
Peers 2: The
admin_peers
RPC call lists 4 peers only, is that expected?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.