randomforest/rchain-node repository overview

docker run -ti randomforest/rchain-node:03-29-18

text below from: https://store.docker.com/community/images/rchain/rchain-node⁠ which seems to have vanished

Node v0.1.3

This release of the RChain Node software includes the peer-to-peer communications network overlay. It will allow you to bring up a node and attach to the public test net. Your new node will then connect itself to other peers in the network.

This release also produces metrics on some communications-related activities in Prometheus format. A local node and metrics visualizer may be started by following the instructions found here. That requires Docker Compose.

By way of demonstration, this release also includes an HTTP server. Eventually, a version of the requests listed here will be implemented, but for now, this serves as an interesting placeholder. Quick Start

The easiest way to get going is to run

docker run -ti rchain/rchain-node

which will pull down and start the latest version of the container. Options

When run as above with no arguments, it behaves as though

--bootstrap rnode://[email protected]:30012 --port 30304

had been specified.

There are several options available which control how the software is seen by the rest of the network:

$ docker run -ti rchain/rchain-node --help RChain Node version 0.1.3 -b, --bootstrap Bootstrap rnode address for initial seed. -h, --host Hostname or IP of this node. -x, --http-port HTTP port. -n, --name Node name or key. -p, --port Network port to use. -s, --standalone Start a stand-alone node (no bootstrapping). --help Show help message --version Show version of this program

Standalone nodes

A node may be run with --standalone to prevent it from attaching to the test net. This is useful for constructing a private network for fun or testing. Specifying --host and --port

Occasionally, the system cannot figure out a reliable way to be contacted from outside the network. Since this is essential to effective peer-to-peer communication, using explicit --host and --port arguments may allow communications. The --port argument is may also be required if running more than one node on a single machine. Source and Further Reading

For more detailed instructions, refer to the documentation at Github, where the source code lives, and on Confluence. Feedback

We welcome feedback on our developer forum. You may file a bug here, too.