Bitcoin solo mining pool (ckpool)
2.0K
How is this Docker image of ckpool-solo different from all of the others?
ckpool has many assembly-language optimisations. To use these, you must build ckpool on the CPU on which it will be running. This Docker image breaks all the rules and does exactly that - builds ckpool inside the container so that it can use all the assembly language optimisations.
Most other ckpool Docker images turn off all assembly-language high-performance optimisations so that the image they create can run on all CPUs.
This image will run on both Intel and ARM CPUs.
Every time you start the Docker container it:
The GitHub for this image is:
https://github.com/pdath/ckpool-solo-docker.
The Docker hub image is:
https://hub.docker.com/repository/docker/pdath/ckpool-solo
This image was designed to be used by:
https://github.com/pdath/knots-ckpool-solo-ckstats-quick-start
There is also a video guide and installation article here:
https://youtu.be/MbCZpps7Ijs
https://pdath.substack.com/p/quick-start-guide-to-solo-mine-bitcoin
Edit ckpool.conf before running.
You can monitor the logs with: docker logs -f ckpool-solo
Content type
Image
Digest
sha256:9f132205f…
Size
28.4 MB
Last updated
about 2 months ago
docker pull pdath/ckpool-solo