[WIP] include parity node via docker #1
Conversation
whilei
commented
Aug 28, 2017
•
whilei
commented
- TODO: setup bootnodes connection for parity and restrict discovery/reserved peers
solution: init dockerfile and chain config
|
@whilei do you think they merge ecip1017 code into master? I didn't check it. If merged, maybe it makes sense to base docker on their existing image and just add chain config and launch scripts? |
|
They did merge our PR to master (openethereum/parity-ethereum#5741), so I based the docker file off their master (https://github.com/paritytech/parity/blob/master/docker/ubuntu/Dockerfile). I didn't see a default JSON config file or example, so based the config on https://github.com/paritytech/parity/wiki/Chain-specification and an example repo https://github.com/5chdn/crossclient-chainspec. See https://github.com/whilei/ecip1017test/blob/1a002d579b94c9dd3eb4d982831bbab293784de8/docker/parity/parity.json#L19 for relevant ecip1017 json config. Still todo is the launch script (and extract that part from current dockerfile) and make sure the config file works. I've been having some network connection issues with parity on my local private network (https://github.com/ethereumproject/homerun/blob/master/example-basedir/green-parity/flags.conf -- parity says: |
|
I mean instead of full compilations you can have just: |
solution: use config generator to make file and add necessary fields like chainID, networkID
solution: use parity/parity image, assumes docker build is from their master branch
solution: include that bootnodes can be specified as a file enables rpc there is no mining option
