Split bitcoind into a separate repo

[meeDamian]

Already done in lncm/docker-bitcoind.

The way it's currently envisioned is:

1. Each minor bitcoind version gets its own Dockerfile in it's own 0.X directory,
2. All bitcoind versions are build atop of lncm/berkeleydb:db-4.8.30.NC which was build through an automated pipeline (amd64 on Docker Hub, and arm using qemu on Travis),
3. amd64 image of bitcoind is build on docker hub upon tagging,
4. arm image of bitcoind is build manually on our RBP,
5. A manifest binding both together is created manually upon both builds completion,

Also, @nolim1t please take a look at https://github.com/lncm/docker-bitcoind/blob/master/0.17/Dockerfile and comment. Note that some things change, ex:

1. /home/bitcoin/.bitcoin is abandoned in favour of the default /root/.bitcoin,
2. upstream maintainers are removed
3. BDB is now an external build stage

TODO for this issue: create Docker Hub automation pipeline that builds amd64 image, so that each 0.X.Y git tag triggers a build of a Dockerfile from 0.X/ folder.

Issue can be closed after:

• build automation is added to lncm/docker-bitcoind
• bitcoind stuff is removed from dockerfiles
• at least one successful bitcoind has been deployed to lncm/bitcoind (with manifest)

[meeDamian]

Also, are you guys okay if I nuke all of these tags: https://cloud.docker.com/u/lncm/repository/docker/lncm/bitcoind and replace them with the new ones, and with more consistent and sensible naming?

[nolim1t]

Don’t nuke all the tags until you build a new arm tag. It will break the setup of boxes.

Please send a new pull request with the new tag name to pi-factory also

[nolim1t]

new bitcoind dockerfile looks good

[meeDamian]

The thing I need to nuke them to set up build automation.

I already have arm built locally, so I can nuke them and then push my local one right away.