Practical overview
When it fits
Use it when you operate a Bitcoin daemon and want to run an ElectrumX server in Docker with configurable data storage and network interfaces.
Who it is for
- Bitcoin node operators who want to provide Electrum-compatible access to daemon data.
- Self-hosters configuring ElectrumX in Docker.
- Operators who need to expose the server's SSL or WebSocket interface, or RPC access for host-side tools.
Documented uses
- Run ElectrumX in a Docker container connected to a configured daemon URL.
- Persist ElectrumX data and certificate files in a mounted host directory.
- Expose SSL or WebSocket access to compatible clients.
- Make RPC available to host-side tools when needed.
Requirements & limits
- A daemon URL with credentials is required in the documented launch configuration.
- The data directory is mounted at /data; existing electrumx.crt and electrumx.key files there are used, or the image generates them when absent.
- Only SSL is exposed by default in the documented configuration; WebSocket, TCP and RPC ports require separate publishing.
- The project documentation strongly discourages exposing unencrypted TCP.
- For host-side RPC access, the README suggests limiting the published port to localhost.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Start the Docker ElectrumX container with SSL access
Launch the image with a mounted data directory, daemon URL and published SSL port.
Before you start
- Docker
- A Bitcoin daemon connection URL with credentials and host port
- A host directory to mount at /data
Steps
Mount the chosen host directory at /data.
Set DAEMON_URL to the daemon URL, including its credentials and address.
Publish port 50002 and run the lukechilds/electrumx image.
Expected outcome
The documented container launch configuration publishes the ElectrumX SSL port and retains its data in the mounted directory. Existing electrumx.crt and electrumx.key files in that directory are used; otherwise, certificate and key files are generated.
Guide limitations
- The guide documents the launch configuration, not a verified successful connection to a daemon or client.
- The daemon URL and credentials must be supplied by the operator.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- lukechilds/docker-electrumx · Official homepage title · retained in its source language

