leonardochaia/docker-monerod

Monerod Docker image based off alpine

Docker Monerod

Run monerod using Docker.

This image clones https://github.com/monero-project/monero and builds it according to instructions.

Usage

Append any monerod params after the image name. i.e:

docker run -it --rm lchaia/monerod --help

Blockchain Volume

The blockchain will get downloaded at /home/monero/.bitmonero, so you should volume-map that path for persistance

Permission issues

If experiencing permission issues on the volume-mapped folder these can be solved with a chown like below:

docker run -it --rm -v /etc/monero-blockchain:/home/monero/.bitmonero \
--entrypoint chown --user root lchaia/monerod monero:monero -R /home/monero/.bitmonero

Docker Compose example

You'll need to modify it for your environment

version: "3"

services:
  monerod:
    image: lchaia/monerod:v0.17.3.2 # or latest and use watchtower to keep up to date
    container_name: monerod
    volumes:
      - /home/my-user/.bitmonero:/home/monero/.bitmonero
    ports:
      - 18080:18080
      - 18089:18089
    command:
      - "--non-interactive"
      - "--restricted-rpc"
      - "--rpc-bind-ip=0.0.0.0"
      - "--rpc-bind-port=18089"
      - "--confirm-external-bind"
      - "--max-concurrency=4"
      - "--public-node"

Copyrights

Code from this repository is released under MIT license. Monero License

Donations

Please consider donating to Monero

docker-monerod's Issues

Paths in Example `docker-compose.yml`

Not a massive issue, just a detail I think is worth pointing out.

In the example docker-compose file, the blockchain volume is bound like this:

volumes:
      - /etc/monero-blockchain:/home/monero/.bitmonero

The /etc directory is intended to be used for static configuration, and isn't expected to grow significantly in size without the user performing some kind of action. It's not really the right place for the blockchain to be stored.

A more appropriate place would be a folder in /var which is intended for things that could vary in size (hence the name). I'm sure most users will edit the file for their machine, but there is no harm in providing a sensible default in case someone has their system setup with /var in a different partition.