> For the complete documentation index, see [llms.txt](https://docs.lumoz.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumoz.org/verifier/setup-verifier-node/setup-node/build-your-own/2.-run-the-node/run-with-docker-recommended-for-multiple-nodes.md).

# Run with Docker(recommended for multiple nodes)

{% hint style="info" %}
If you don’t have Docker yet, [download it here](https://www.docker.com/products/docker-desktop).
{% endhint %}

## **Step1:  Create the `.env` file**

```Bash
NODE_OPERATOR_PRIVATE_KEY={put the private key of your node operator wallet here}
NODE_OWNER_PRIVATE_KEY={put the private key of your node owner wallet here}
JSONRPC_URL={your_rpc_url}
ADDRESS_OF_OWNER_OR_OPERSTOR={put the wallet address of your node owner or operator}
```

## **Step2:  Create the** `docker-compose.yml` file

```Bash
version: "3.5"
services:
  lumoz-Verifier-node:
    container_name: lumoz-Verifier-node
    image: lumozorg/lumoz-verifier-node:latest
    environment:
      - WALLET_PRIVATE_KEY=${NODE_OPERATOR_PRIVATE_KEY}
      - JSONRPC_URL=${JSONRPC_URL}
    command:
      - "/bin/sh"
      - "-c"
      - "/app/verifier-node node-runner"
  lumoz-Verifier-node-claim:
    container_name: lumoz-Verifier-node-claim
    image: lumozorg/lumoz-verifier-node:latest
    environment:
      - JSONRPC_URL=${JSONRPC_URL}
      - WALLET_PRIVATE_KEY=${NODE_OWNER_PRIVATE_KEY}
      - OWNEROROPERATOR=${ADDRESS_OF_OWNER_OR_OPERSTOR}
    command:
      - "/bin/sh"
      - "-c"
      - "/app/verifier-node reward-claimer"
```

## **Step3:** Run your node.

#### `sudo docker-compose -f docker-compose.yml up -d lumoz-Verifier-node`

## **Step4:** Run the reward claim program.

`sudo docker-compose -f docker-compose.yml up -d lumoz-Verifier-node-claim`

Congratulations, your node is running successfully.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.lumoz.org/verifier/setup-verifier-node/setup-node/build-your-own/2.-run-the-node/run-with-docker-recommended-for-multiple-nodes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.