You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All settings are passed in as ENV vars (no need for ENV folder)
Runs ElectrumX directly as PID 1 instead of bash -> daemon
Interactive Docker sessions attach directly meaning Control-C works
Interactive Docker sessions get ElectrumX output to STDOUT
ElectrumX output will be piped to normal Docker logging tools
You shouldn't dockerize a daemon, the Docker image itself should be daemonized
Reproducible builds: separate branch for each release (followtheart container builds current master)
Up to date
Pulling from Docker Hub will pull the latest ElectrumX release. You can also specify a tag to pull specific older ElectrumX releases.
The latest followtheart build on Docker Hub is 6 months out of date.
Secure
If no SSL cert is provided one will be automatically generated on first boot.
Following these rules makes the image much easier to orchestrate in other Docker projects (e.g Dockerized Vertcoin Electrum Server), it's also currently the most used ElectrumX image on Docker Hub.
Let me know if you'd like to link to this image instead and I'll happily submit a PR.
The text was updated successfully, but these errors were encountered:
I created my own Docker image (
lukechilds/electrumx
) due to some issues I had with the current image recommended in the readme (followtheart/electrumx
).The followtheart image doesn't follow Docker best practices and is also quite large and out of date. I believe my image is better because:
Size
lukechilds/electrumx
: 40MBfollowtheart/electrumx
: 175MBFollows Docker conventions
Control-C
worksUp to date
Pulling from Docker Hub will pull the latest ElectrumX release. You can also specify a tag to pull specific older ElectrumX releases.
The latest followtheart build on Docker Hub is 6 months out of date.
Secure
If no SSL cert is provided one will be automatically generated on first boot.
Following these rules makes the image much easier to orchestrate in other Docker projects (e.g Dockerized Vertcoin Electrum Server), it's also currently the most used ElectrumX image on Docker Hub.
Let me know if you'd like to link to this image instead and I'll happily submit a PR.
The text was updated successfully, but these errors were encountered: