# Re standalone docker

This page contains information about building and running a Re node in a standalone way.

### Prerequisites[​](https://docs.neutron.org/neutron/build-and-run/neutron-docker#prerequisites) <a href="#prerequisites" id="prerequisites"></a>

* [Docker engine](https://docs.docker.com/get-docker/)
* Golang v1.19 ([go releases and instructions](https://go.dev/dl/)).

### Build and run[​](https://docs.neutron.org/neutron/build-and-run/neutron-docker#build-and-run) <a href="#build-and-run" id="build-and-run"></a>

#### 1. Make sure you have the required Golang version[​](https://docs.neutron.org/neutron/build-and-run/neutron-docker#1-make-sure-you-have-the-required-golang-version) <a href="#id-1-make-sure-you-have-the-required-golang-version" id="id-1-make-sure-you-have-the-required-golang-version"></a>

```
go version
```

#### 2. Clone Re  repository and cd into it[​](https://docs.neutron.org/neutron/build-and-run/neutron-docker#2-clone-neutron-core-repository-and-cd-into-it) <a href="#id-2-clone-neutron-core-repository-and-cd-into-it" id="id-2-clone-neutron-core-repository-and-cd-into-it"></a>

```
git clone https://github.com/jim380/Re.git
cd Re
```

#### 3. Build a Re node image[​](https://docs.neutron.org/neutron/build-and-run/neutron-docker#3-build-a-neutron-node-image) <a href="#id-3-build-a-neutron-node-image" id="id-3-build-a-neutron-node-image"></a>

```
make build-docker-image
```

#### 4. Run a Re node as a docker container[​](https://docs.neutron.org/neutron/build-and-run/neutron-docker#4-run-a-neutron-node-as-a-docker-container) <a href="#id-4-run-a-neutron-node-as-a-docker-container" id="id-4-run-a-neutron-node-as-a-docker-container"></a>

```
make start-docker-container
```

A Re node is now running in the background. To see the app logs, run:

```
docker ps
```

And use the `re-node` container ID in the following command:

```
docker logs -f <re-node-contained-id>
```

To stop the node, run

```
make stop-docker-container
```

### Usage[​](https://docs.neutron.org/neutron/build-and-run/neutron-docker#usage) <a href="#usage" id="usage"></a>

#### Ports[​](https://docs.neutron.org/neutron/build-and-run/neutron-docker#ports) <a href="#ports" id="ports"></a>

The Re node exposes several ports to be used by you and your applications:

* 1317:1317 — the REST server;
* 26657:26657 — the Tendermint RPC server;
* 26656:26656 — the Tendermint P2P server;
* 9090:8090 — the gRPC server.

#### Interaction with the node using red[​](https://docs.neutron.org/neutron/build-and-run/neutron-docker#interaction-with-the-node-using-neutrond) <a href="#interaction-with-the-node-using-neutrond" id="interaction-with-the-node-using-neutrond"></a>

The Re node is available to be interacted with using `red` command. The following command will install `red` on your computer:

```
make install
```

This command builds the `red` executable using the latest version of the Re Protocol and installs the resulting binary in your GOBIN directory. Ensure that GOBIN is defined and included in the PATH environment variable. This ensures that the installed binary can be accessed globally on your system. If you encounter any issues during this process, troubleshoot them by verifying that your Golang-related environment variables are correctly set.

After the installation process is complete, the `red` executable is ready to be used:

```
red query bank total
```

#### Making transactions[​](https://docs.neutron.org/neutron/build-and-run/neutron-docker#making-transactions) <a href="#making-transactions" id="making-transactions"></a>

There are several accounts added at the genesis state that possess RE and are at your service. See the[ genesis init script](https://github.com/jim380/Re/blob/master/network/init.sh) to find out more details about it. The following command will list all the preallocated addresses:

```
docker exec <re-node-contained-id> red keys list --keyring-backend test --home data/test-1/
```

We suggest you add the accounts from the init script mentioned above to your local test keyring to make them useful directly from the command line. To do so, copy a mnemonic from the script and use it in a keypair recovery procedure:

```
red keys add <name> --recover --keyring-backend test
> Enter your bip39 mnemonic
```

After that, you'll be able to make transactions using any of the accounts and Queries


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cyphercore.gitbook.io/re/build-and-launch/re-standalone-docker.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.