-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ethereum/client-python containers are out of date #5
Comments
hi @konradkonrad , would it possible to elaborate more on this issue? It would be very helpful if the last workable version and the problem of the outdated client are known. |
Until we get access to |
I am running separate instances of pyethapp on a locally defined node. I'm using the development version in a virtual environment. I'm still pretty new to ethereum and don't entirely get what bootstrap nodes are for. From the docker config file it appears that all nodes, clients and miners, connect to that node. I'm guessing that it stores the initial blockchain, starting with the genesis block? |
You can build the container with `make setup`.
@SethVgr @ChihChengLiang please try the version in https://github.com/konradkonrad/docker-pyeth-cluster/tree/local-container (i.e.
Bootstrap nodes are used to solve the initial discovery problem.
All nodes in a network need to agree on a common genesis hash. In our case we provide a custom genesis_hash in all |
I've also seen that in the docker example the bootstrap node receives a private key as a command line argument.
Can pyethapp generate such addresses more conveniently? In my case I need to setup multiple private networks and need a new bootstrap node with a distinct key for each. |
Hey @SethVgr -- the private key from configuration (-flag) is necessary, since we want to be able to determine the public enode-address for our custom bootstrap-node.
I hope, this is convenient enough? Anyway, please move such Q/A to our gitter channel: https://gitter.im/ethereum/pyethapp Could you test the |
Thanks @konradkonrad, I have removed the old ethereum/pyethapp from docker and reran it with:
and got the results below. An eth node apparently can't connect to the network. It may have been my fault as I only left docker running for ~15 minutes. Thanks for the explanation over address generation. Is there something like a reference guide on how to use pyethereum? offering some basic examples as well.
|
@SethVgr above log still shows the outdated pyethapp version (1.0.2). Please follow these steps:
|
Thanks @konradkonrad , it works perfectly for me. |
Use a local container to workaround #5
Thanks for your feedback @ChihChengLiang -- I merged the changes into master with #7 |
@konradkonrad I've downloaded version (1.0.3) of pyethapp. See the logs below (it still reports that there are not enough peers (there should be at least 5?)):
|
State: the current code base builds a container locally -- the upstream container issue (dockerhub/ethereum/client-python) still persists.
The text was updated successfully, but these errors were encountered: