| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
parent directory.. | ||||
You can run the graph-node docker image either in a complete setup controlled by Docker Compose, or, if you already have an IPFS and Postgres server, by itself.
The Docker Compose setup requires an Ethereum network name and node to connect to. By default, it will use mainnet:http://host.docker.internal:8545 in order to connect to an Ethereum node running on your host machine. You can replace this with anything else in docker-compose.yaml.
After you have set up an Ethereum node—e.g. Ganache or Parity—simply clone this repository and run
docker-compose upThis will start IPFS, Postgres and Graph Node in Docker and create persistent data directories for IPFS and Postgres in ./data/ipfs and ./data/postgres. You can access these via:
Once this is up and running, you can use graph-cli to create and deploy your subgraph to the running Graph Node.
We do not currently build native images for Macbook M1, which can lead to processes being killed due to out-of-memory errors (code 137). Based on the example docker-compose.yml is possible to rebuild the image for your M1 by running the following, then running docker-compose up as normal:
Important Increase memory limits for the docker engine running on your machine. Otherwise docker build command will fail due to out of memory error. To do that, open docker-desktop and go to Resources/advanced/memory.
# Remove the original image docker rmi graphprotocol/graph-node:latest # Build the image ./docker/build.sh # Tag the newly created image docker tag graph-node graphprotocol/graph-node:latest
docker run -it \
-e postgres_host=<HOST> \
-e postgres_port=<PORT> \
-e postgres_user=<USER> \
-e postgres_pass=<PASSWORD> \
-e postgres_db=<DBNAME> \
-e ipfs=<HOST>:<PORT> \
-e ethereum=<NETWORK_NAME>:<ETHEREUM_RPC_URL> \
graphprotocol/graph-node:latest| Back | FazBrowse Home | New Git URL |