CryptoCoinsInfoClub.com

Docker Hub Ethereum/client-go

Ethereum Auf Docker | Creativstatt

Ethereum Auf Docker | Creativstatt

Publiziert am 12/02/2017 von Michael Sendrowski Die Ethereum Clients, wie hier geth, entwickeln sich derzeit rasend schnell. So schnell, das die Anleitung hier auch schon nicht mehr aktuell ist. Mit der aktuellen geth Version 1.5.9 kann Alpine hier nicht mehr als Basis genutzt werden. Es wird eine libusb Library bentigt die es jedoch unter UBUNTU gibt. Nachteil ist, das nun das neue Zielimage 230MB gro geworden ist. Blockchain ist derzeit ein top aktuelles Thema. Banken, Versicherungen, Internet der Dinge, Energie- und Verkehrsunternehmen versuchen sich an dem Thema. Einen ersten verstndlichen Erklrungsversuch findet man hier: Was man damit alles machen kann scheint schon phantastisch. Doch was wirklich dran ist und welche Mglichkeiten damit erffnen zeigt sich erst im ersten praktischen Einsatz. Was man dazu braucht ? Eine private Blockchain die hier mit Hilfe von Docker auf einem Raspberry Pi Cluster erzeugt wird. Damit Ethereum genutzt werden kann wird zunchst ein Ethereum Client bentigt. Dieser wird hier in einem Docker Image erstellt und luft spter im Raspberry Pi Cluster. Damit das neue Image mglichst klein gehalten wird, erfolgt die Erstellung in einem RUN Step. So bleibt das neue Image bei < 60MB ! Von Versuchen, das Source Verzeichnis mit ADD in das Image zu Linken kann abgeraten werden. Alle Versuche landen bei ber 700MB. Zur Erstellung folgenden Inhalt in das File Dockerfile-alpine kopieren: apk add git go gcc make musl-dev nano && \ git clone && \ (Alternative ist zu empfehlen, ein eigenesBasis Image zu erstellen als ein Image zu Docker Hub zu laden) docker build -f Dockerfile-alpine -tmicsen/ethereum-alpine:v1 . erstellen und zum Test einmal starten mit Im Prompt den eigentlichen Ethereum Client mit ./geth starten: Das Docker Image besitzt nun den bentigten Continue reading >>

Building Private Ethereum Networks With Docker Compose

Building Private Ethereum Networks With Docker Compose

In my previous article about building a blockchain application , I shared some of the tools, tips and techniques I used to create an end-to-end blockchain web application. Lets hone in on a specific part of that and explain in more depth how I built an underlying Ethereum private blockchain for testing purposes. I mentioned that I predominantly used testrpc to stand up a simple, single-node Ethereum instance which had the APIs exposed and some accounts pre-filled with Ether for testing. Testrpc is a great tool, super simple and fast to get started, which makes it ideal for development and if you are new to the tech. However there are some situations where you might want some extra flexibility or you need to test different scenarios where you require a more production like setup. These include - Testing the effects of a network of nodes (e.g. a multi-node Ethereum cluster with each node in sync with other nodes via the P2P protocol) Access to other Ethereum APIs, for example the management API Access to the Ethereum JavaScript Console The confidence of developing against a full Geth node Easier integration with or ability to test alongside other tools or technology such as IPFS If you find yourself having to set up a private Ethereum cluster (as I did) youll find that its not actually a straightforward process. While there are one or two pretty clear tutorials out there as well as some scripts both for me had some problems. The scripts prefer that you are running Ubuntu, the preferred/recommended platform for Ethereum and the tutorials contain anywhere between 5-20 steps. I wanted a simple, repeatable and cross platform way to bring up and tear down my clusters. Enter Docker and Docker Compose . Today Im announcing our open-sourced ethereum-docker which contains a bunch Continue reading >>

Building An Ethereum Playground With Docker (part 2dockerimage)

Building An Ethereum Playground With Docker (part 2dockerimage)

@vertigobr Founder & CTIO, disrupting things for fun. Building an Ethereum playground with Docker (part 2 DockerImage) I have updated this article on December/2017. I no longer create a custom Docker image, because Ethereum official image already brings an all-tools version that includes bootnode and other treats. This is the second article in an ongoing series Building an Ethereum Playground with Docker. The articles already published are: We will cover using the official ethereum/go-ethereum Docker image, playing with Ethereum Wallet, provisioning the ethereum nodes on public clouds and deployment of a sample app. This article uses " ethereum/client-go " Docker image to run several Ethereum nodes locally (and safely). It also assumes you have a Docker engine available to you (and know a bit about it), probably after installing Docker for Mac or Docker for Windows on your notebook. All sources are located in . There is a public official image "docker pull ethereum/client-go" that will serve as the base of this work. We will create scripts with some functionality and configuration options to make it generally useful for our evil machinations. This original public base image is a nice piece of work: you can use it to participate on the main public Ethereum network with a simple command: The starting point is the creation of a "genesis.json" file that defines the genesis block of the blockchain. The "genesis.sh" script does that for you, and it can be edited to provide custom values for some variables Some variables on the top of this script can be modified to define your very own genesis block, the main point being that all containers will mount the same genesis.json file when launched with the helper scripts. Nodes that share the same genesis block and are capable of f Continue reading >>

Ryptocurrency Development Analysis

Ryptocurrency Development Analysis

Geth version: `geth version 1.8.4-unstable` deploying a node using puppeth should pull relevant docker images from dockerhub and deploy the geth node on the server with network information If you need to pull the newest `ethereum/go-client` on the server (> v1.8.3), you get a permissions issue as follows: What would you like to do? (default = stats) 1. Tear down Nginx on [email protected] 2. Tear down Ethstats on [email protected] What would you like to deploy? (recommended order) 4. Explorer Chain analysis webservice (ethash only) 5. Wallet Browser wallet for quick sends 6. Faucet Crypto faucet to give away funds 7. Dashboard Website listing above web-services Which server do you want to interact with? Where should data be stored on the remote machine? Which TCP/UDP port to listen on? (default = 30303) How many peers to allow connecting? (default = 512) How many light peers to allow connecting? (default = 256) What should the node be called on the stats page? Found orphan containers (ls_ethstats_1, ls_nginx_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the remove-orphans flag to clean it up. Status: Downloaded newer image for ethereum/client-go:latest Step 2/4 : ADD genesis.json /genesis.json 1 // Copyright 2017 The go-ethereum Authors Step 3/4 : RUN echo geth cache 512 init /genesis.json > geth.sh && echo $geth networkid 65170 cache 512 port 30303 maxpeers 512 lightpeers=256 lightserv=50 ethstats test_bootnode:[email protected] targetgaslimit 0 gasprice 0 >> geth.sh /bin/sh: cant create geth.sh: Permission denied Service bootnode failed to build: The command /bin/sh -c echo geth cache 512 init /genesis.json > geth.sh && echo $geth networkid 65170 cache 512 port 30303 maxpeers 512 lightpeers=256 Continue reading >>

Ethereumdocker(geth,parity)

Ethereumdocker(geth,parity)

Help us understand the problem. What is going on with this article? More than 1 year has passed since last update. docker pull ethereum/client-go #tagdefaultlatestUsing default tag: latestlatest: Pulling from ethereum/client-go88286f41530e: Pull complete 528f0dd33bed: Pull complete 8b00e08f6a7a: Pull complete Status: Downloaded newer image for ethereum/client-go:latestdocker images # docker imageREPOSITORY TAG IMAGE ID CREATED SIZEethereum/client-go latest 34fe6352736b 7 hours ago 35.9MB docker rundocker run -d --name ethereum-node -v $HOME/ethereum-data:/root \ -p 8545:8545 -p 30303:30303 \ ethereum/client-go --fast --cache=512CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES8dd333c2fb47 ethereum/client-go "geth --fast --cac..." 3 seconds ago Up 2 seconds 0.0.0.0:8545->8545/tcp, 0.0.0.0:30303->30303/tcp, 8546/tcp, 30303/udp ethereum-node -v docker$HOME/ethereum-data/root docker nao docker logs -f ethereum-node #fCtrl+CWARN [09-13|15:17:54] No etherbase set and no accounts found as default INFO [09-13|15:17:54] Starting peer-to-peer node instance=Geth/v1.7.0-unstable/linux-amd64/go1.9INFO [09-13|15:17:54] Allocated cache and file handles database=/root/.ethereum/geth/chaindata cache=512 handles=1024INFO [09-13|15:17:54] Writing default main-net genesis block INFO [09-13|15:18:01] Initialised chain configuration config="{ChainID: 1 Homestead: 1150000 DAO: 1920000 DAOSupport: true EIP150: 2463000 EIP155: 2675000 EIP158: 2675000 MINFO [09-13|15:36:30] Imported new block receipts count=4 elapsed=1.033ms bytes=16 number=173656 hash=96bf2af1d7f6 ignored=0INFO [09-13|15:36:30] Imported new state entries count=1160 elapsed=7.944ms processed=246145 pending=7605 retry=0 duplicate=0 unexpected=0 / #/ # geth attachWelcome to the Geth JavaScript console! > eth.getBlock(100)>{ d Continue reading >>

Go Ethereum - How Can I Completely Automate A Docker Image And Dockerfile For A Geth Test Network - Ethereum Stack Exchange

Go Ethereum - How Can I Completely Automate A Docker Image And Dockerfile For A Geth Test Network - Ethereum Stack Exchange

How can I completely automate a Docker image and Dockerfile for a geth test network I would like to create a Docker image for a test network that has everything ready to go - pre-created accounts with ether already allocated. The problem is there doesn't seem to be a way to do this the Docker Way(tm). In order to create ether out of thin air, I have to put addresses in the genesis.json 'alloc' section. In order to get the addresses, I have to create accounts with multiple invocations of geth and then manually edit genesis.json. Manual steps are not the Docker Way(tm), you are supposed to create a Docker file that does all these steps automatically. My current best bet seems to be to to create a script that creates the accounts I need and the gets the account addresses from the geth command line option for that and then edits genesis.json on the fly. That seems... rather crude, and adds more tools to the docker image to do this (at least something that can parse JSON). Creation of accounts is not idempotent, so I can't just run the same script every time I start the container. I'm sure the geth community has solved this problem for their own automated testing. Please share :-) I've read everything on the first page of this Google Search . They all have manual steps, which doesn't work for automation that Docker and automated test systems demand. Do you mind if the docker image always uses the same addresses? You could allocate the Ether, and just either have the private key files already in the keystore, or programmatically add them with a plaintext private key. Tjaden Hess Feb 21 '16 at 2:04 Same addresses is fine. I just use indexes in my web3.js code. However if you note in the geth documentation, creation and importation of accounts mucks with the indexes. Paul S Fe Continue reading >>

Docker Parity Ethereum Documentation

Docker Parity Ethereum Documentation

Docker containers for Parity are available via Docker Hub : $ docker search parity/parityNAME DESCRIPTION STARS OFFICIAL AUTOMATEDparity/parity Parity is Ethcore's initial fully-featured... 0parity/rust Rust stable, beta and nightly for GitLab C... 0 [OK]parity/snapcraft Docker image for build snap application (U... 0 [OK]parity/rust-arm RUST for GitLab CI runner (ARM architecture) 0 [OK] To get a list of available versions, use curl and jq: $ curl -sS '| jq '."results"[]["name"]' | sort"nightly""v1.6.8""v1.6.9""v1.6.10""v1.7.0" To run Parity with an interactive pseudo-tty shell, run: Parity can be configured using either the CLI options or a config file . Should the CLI flags and the config file disagree about a setting, the CLI takes precedence. You can list all CLI options by running: For Docker specific options, please refer to the Docker documentation , or run docker --help or docker run --help. To publish Paritys ports to the host machine, use the -p option: $ docker run -ti -p 8180:8180 -p 8545:8545 -p 8546:8546 -p 30303:30303 -p 30303:30303/udp parity/parity:v1.7.0 --ui-interface all --jsonrpc-interface all For example, this will expose the User Interface, the JSONRPC-API, and the listen port to the host. Now you can open Parity UI from the Docker host computer to access the Parity Wallet. To enable external discovery where desired (for example for PoA sealing nodes), specify the external IP by appending the flag --nat extip:133.3.3.37, where 133.3.3.37 is to be replaced by your actual external IP of the host. To pass further operating options to Parity, simply append them to the docker run command: $ docker run -ti parity/parity:v1.7.0 --no-ui --no-dapps --no-discovery In this case, it disables the Wallet, the DApps Server, and discovery. For more complex node Continue reading >>

Released: Geth 1.4 Rc2 - Ethereum

Released: Geth 1.4 Rc2 - Ethereum

Among others, this second release candidate also contains the Geth release oracle , which is a multi-sig Ethereum contract tracking the latest Geth releases. Its goal is to allow Geth clients to periodically check for new releases on-chain, without any centralized server. New releases need to be signed off by 2 out of 3 current signers (Jeff/@obscuren, Felix/@fjl and Peter/@karalabe) to be accepted by the oracle and users be notified of it. Note, that we do not do any automatic upgrades, only display a small CLI notification to the user every once in a while. The verified contract is live at 0xFA7B9770Ca4cb04296Cac84F37736d4041251CDF . The full contract ABI is available here , but you can also use a reduced ABI that just contains the list of signers and the current release version. This is great stuff. You might want to give a head's up to the Mist team (if you haven't already), they were looking into something like this with a feature suggestion I made awhile back: Actually we've discussed it and decided against it. The reason is that Go builds aren't AFAIK binary reproducible (meaning that a rebuild produces a different hash, in part because Go uses random iterated maps). This could cause confusion with people who aren't aware of this, and also interesting corner cases where downloading from an Ubuntu PPA will have a different hash than the distributed binary from GitHub, and even different between PPA builds and Ubuntu versions. In general, we just wanted an easy way to notify people that they are running stale software and wanted to keep clear of any auto-update mechanisms that could have unforeseen vulnerabilities. In the future we can most definitely consider polishes, further updates, etc to the version oracle, but we wanted to start out small and grow as need b Continue reading >>

Vulnerability Spotlight: Multiple Vulnerabilities In The Cpp And Parity Ethereum Client

Vulnerability Spotlight: Multiple Vulnerabilities In The Cpp And Parity Ethereum Client

Vulnerability Spotlight: Multiple Vulnerabilities in the CPP and Parity Ethereum Client Talos Group - January 9, 2018 - 1 Comment Talos is disclosing the presence of multiple vulnerabilities in the CPP and the Parity Ethereum clients. TALOS-2017-0503 / CVE-2017-14457 describes a denial of service vulnerability and potential memory leak in libevm. The function is not currently enabled in the default build. This vulnerability only affects nodes which have manually enabled it during build time. TALOS-2017-0508 / CVE-2017-14460 is an overly permissive cross-domain (CORS) whitelist policy vulnerability in the Ethereum Parity client. It can lead to the leak of sensitive data about existing accounts, parity settings and network configurations, in addition to accounts and parity settings modifications, if certain APIs have been turned on. Further on, TALOS-2017-0464 TALOS-2017-0471 / CVE-2017-12112 CVE-2017-12119 describe multiple Authorization Bypass Vulnerabilities which an attacker could misuse to access functionality reserved only for users with administrative privileges without any credentials. Finally, Talos found TALOS-2017-0471 / CVE-2017-12119, another denial of service vulnerabilities in the CPP-Ethereum JSON-RPC implementation. A specially crafted json request can cause an unhandled exception resulting in a denial of service. Continue reading >>

Doku@wiki.b0x.it Doku/programming - Ethereum

[email protected] Doku/programming - Ethereum

For a deep dive into Smart Contracts see Ethereum Smart Contracts .A collection of recent and past ICOs can be found here: Ethereum ICOs . docker pull ethereum/client-go:v1.7.3 pulls a geth image docker run -ti -d -p 127.0.0.1:8545:8545 --name parity -v /opt/ethereumForParity:/root parity/parity:v1.8.4 --jsonrpc-interface '0.0.0.0' --jsonrpc-hosts="all" -d /root runs a parity node docker run -d -p 127.0.0.1:8545:8545 -p 30303:30303 --name geth -v /opt/ethereumForGeth:/root ethereum/client-go:v1.7.3 --rpc --cache=2048 --syncmode=fast --rpcaddr=0.0.0.0 --rpcport=8545 mounts a data volume into the container; the rpc port is only available at the localhost domain: internally the container listens on all addresses (it must in particular listen to the ip of eth0 in the container!); the volume is available under /root in this case (see here ), for more information on the geth docker image docker run -d -p 136.243.110.29:18545:8545 -p 30301:30303 --name geth-etc -v /opt/classic:/opt unscipreneur/ethereum-classic-geth --rpc --data-dir /opt/.ethereum --cache=2048 --rpcaddr=0.0.0.0 --rpcport=8545 runs a classic geth instance and opens the rpc interface to the public docker exec -ti geth-eth --exec 'loadScript("/root/scripts/getInvestors.js")' attach runs a script (/root/scripts/getInvestors.sh) against the geth node. This script could be: var myschemeContract = web3.eth.contract([{"constant":true,"inputs":[],"name":"getNumInvestors","outputs":[{"name":"a","type":"uint256"}],"type":"function"},{"inputs":[],"type":"constructor"}]); var c = myschemeContract.at("0xa327075af2a223a1c83a36ada1126afe7430f955"); console.log(c.getNumInvestors()); Running a test instance of Ethereum with docker mkdir -p /opt/ethereumTest/.ethereum/geth and touch /opt/ethereumTest/.ethereum/geth/genesis.json Continue reading >>

Geth-node

Geth-node

or copy the sources to your docker host and build on your own. docker build --force-rm -t blakeberg/geth-node . docker run -d -h geth --name geth -p 20022:22 -p 8545:8545 blakeberg/geth-node Connect with ssh use the port that was just located: if you us boot2docker you shoud add to your /etc/hosts under Windows or Mac OS X the IP and host name of the boot2docker VM 192.168.99.100 geth (IP to verify) Decentralized platform that runs smart contracts or especially applications that run exactly as coded without downtime, censorship, fraud or third party smog. Applications so called Dapps need just an Ethereum client node which is connected in Ethereum networks and syncs the Blockchain - the decentralized public ledger and global world computer. A Dapp contains one or more contracts and a graphical user interface to handle it. The Ethereum node can be started inside the container within a ssh session or outside from host via docker exec command. It will need a long time (3+ hours) to sync all blocks from testnet about 2,6GB for full blockchain ~/.ethereum/testnet/chaindata. You can see the state via JavaScript console type eth.syncing Instead of geth ... and geth attach you can run get console to get both logging and interactive JavaScript console. If you have an issue with cross origin requests you can allow all domains with parameter --rpccorsdomain "*" and if you can't connect to geth node you can allow all adresses with parameter --rpcaddr "0.0.0.0" The url was set as --rpccorsdomain for a dapp running in container "meteor-nodejs". (link below) start ethereum node: nohup geth --testnet --rpc --rpcaddr "geth" --rpccorsdomain "& try JSON RPC API type curl -X POST --data '{"jsonrpc":"2.0","method":"web3_clientVersion","params":[],"id":67}' and will get a JSON Response {"id Continue reading >>

Geth Ethereum Linux - Bitcoin

Geth Ethereum Linux - Bitcoin

Geth ethereum linux - bitcoin Install and Ethereum node on Ubuntu 16. 2 . Both are command line applications. Put your ethereum address at bat file. Or cuda miner cudaminer. Now exit terminate gethcontrol D on linux) and add your account to mytestnet genesis. Ethereum Classic Ethereum ClassicETC) . Geth attachdatadir testnet geth. Geth , Ethereum. You can find it in the. Build Your Own Raspberry Pi Ethereum Full NodeGo Client. Note that the wallet file is not stored. Ethereum. You need geththis is the Go ethereum implementation) and solcthis is a compiler you need to compile smart contracts written in solidity. The code is exceptionally portable has been used successfully on a very broad range of operating systems hardware. However, it s quite popular amidst coders. Install geth git clone com ethereum go ethereum cd go ethereum make geth. Json datadirethereum data. Javascript Console: geth can be launched with an interactive console, that provides a javascript runtime environment exposing a javascript API to interact with your node Installing GethBuilding EthereumMining. Getting started with ethereum Ivo van der Wijk 16. Ethereum Windows USERPROFILE AppData Roaming Ethereum. 7 cdtmp curlLO googleapis. This specifies the possible clients and the platforms they support. Geth ethereum linux. Go ethereumgeth) requires a specific version of Go contains multiple commands. There are also various distros of Linux that can be usednot covered here. Datadir and you will see a result like on the screenshot above with the full path. Geth ethereum linux. Gz sudo rmfr geth linux amd64 1. Gethused in the Ethereum Wallet) saves its internal states for the main network in the chaindata directory. Gz tarCusr local xvf go1. 1 documentation Both geth ethminer implement automatic DAG genera Continue reading >>

Docker Ethereum Homestead 0.1 Documentation

Docker Ethereum Homestead 0.1 Documentation

We are hosting latest development snapshots (and in the future alsoreleases) at docker hub. You can run these images as follows: Before running the image, you should pull the latest version and preparethe data directories: # get the lastest version from dockerhub (redo for updates).docker pull ethereum/client-cpp# create mountable datadirs; blockchain/account data will be stored theremkdir -p ~/.ethereum ~/.web3 These steps need to be done only once. For upgrading to a new version dothe docker pull ... again. docker run --rm -it \ -p 127.0.0.1:8545:8545 \ -p 0.0.0.0:30303:30303 \ -v ~/.ethereum:/.ethereum \ -v ~/.web3:/.web3 \ -e HOME=/ \ --user $(id -u):$(id -g) \ ethereum/client-cpp This will write data to ~/.ethereum and ~/.web3/ on your host and runthe client with your users permissions. For most cases this should besufficient and the client should behave exactly as if run from a local build. If you want the rpc port reachable from the network (not recommended, never do thisif you have valuable data or private keys on your machine), replace-p 127.0.0.1:8545:8545 by -p 0.0.0.0:8545:8545. For convenience, you can create the file /usr/local/bin/docker-eth with thefollowing content: #!/usr/bin/env shmkdir -p ~/.ethereum ~/.web3if ! id -nG $(whoami)|grep -qw "docker"; then SUDO='sudo'; else SUDO=''; fi$SUDO docker run --rm -it \ -p 127.0.0.1:8545:8545 \ -p 0.0.0.0:30303:30303 \ -v ~/.ethereum:/.ethereum \ -v ~/.web3:/.web3 \ -e HOME=/ \ --user $(id -u):$(id -g) \ ethereum/client-cpp [email protected] And make it executable with chmod +x /usr/local/bin/docker-eth. Now you canstart the client with: Note: The docker-eth command will accept the same flags as the raw ethcommand. If you want to attach to the node, you can either just use mist (it willdetect the node automatically), use geth Continue reading >>

Introduction To Docker Tutorial | Toptal

Introduction To Docker Tutorial | Toptal

#DevOps #Docker #Sandboxing #SystemIsolation If you like whales, or are simply interested in quick and painless continuous delivery of your software to production, then I invite you to read this introductory Docker Tutorial. Everything seems to indicate that software containers are the future of IT, so lets go for a quick dip with the container whales Moby Dock and Molly . Docker, represented by a logo with a friendly looking whale, is an open source project that facilitates deployment of applications inside of software containers. Its basic functionality is enabled by resource isolation features of the Linux kernel, but it provides a user-friendly API on top of it. The first version was released in 2013, and it has since become extremely popular and is being widely used by many big players such as eBay, Spotify, Baidu, and more . In the last funding round, Docker has landed a huge $95 million . The philosophy behind Docker could be illustrated with a following simple analogy. In the international transportation industry, goods have to be transported by different means like forklifts, trucks, trains, cranes, and ships. These goods come in different shapes and sizes and have different storing requirements: sacks of sugar, milk cans, plants etc. Historically, it was a painful process depending on manual intervention at every transit point for loading and unloading. It has all changed with the uptake of intermodal containers. As they come in standard sizes and are manufactured with transportation in mind, all the relevant machineries can be designed to handle these with minimal human intervention. The additional benefit of sealed containers is that they can preserve the internal environment like temperature and humidity for sensitive goods. As a result, the transportation Continue reading >>

Gregbkr/ethereum-nodes-docker

Gregbkr/ethereum-nodes-docker

Introducing the Tidelift Subscription . Professional-quality security updates and maintenance for the open source projects you depend on. In few commands: (thx to docker compose ;) make a transaction in python (transfert test eth between the nodes) Data stays on host volumes: container nodes can be destroy without lossing the data --> easy version migration Auto unlock wallets when container is starting (please use firewall to protect your prod nodes!) More info: you can find an overview of that setup on my blog: git clone eth && cd eth docker volume create --name eth_gethtestdocker volume create --name eth_paritytest Use already existing account and password (nice so you don't have to load ethtest) cp -r gethtest/* /var/lib/docker/volumes/eth_gethtest/_data/cp -r paritytest/* /var/lib/docker/volumes/eth_paritytest/_data/ docker run --rm -it -v eth_paritytest:/root/.parity ethcore/parity --testnet account newls /var/lib/docker/volumes/eth_paritytest/_data/testnet_keys/ <-- your test wallet is heredocker run --rm -it -v eth_gethtest:/root/.ethereum ethereum/client-go --testnet account newls /var/lib/docker/volumes/eth_gethtest/_data/testnet/keystore/ <-- your test wallet is here docker run -d --name geth0 -v eth_gethtest:/root/.ethereum ethereum/client-go --testnetdocker exec -it geth0 bash -c "geth --testnet --password <(echo -n notsecure) account new"docker stop geth0 && docker rm geth0 echo -n 'notsecure' > /var/lib/docker/volumes/eth_paritytest/_data/testnet_keys/mypass <-- unsure that there is no space or new line in file: don't use nano, it leave a new line!! docker exec eth_paritytest_1 /build/parity/target/release/parity --testnet account listdocker exec eth_gethtest_1 geth --testnet account list Use the python script to check data and to send eth between the tw Continue reading >>

More in ethereum