bmmbmm01/sftp2 repository overview

⁠Bitcoin Knots GUI — Docker Web Desktop

Image: bmmbmm01/bitcoinknotsgui
Bitcoin Knots target release: 29.4.3.knots20260508
Platform: Linux x86-64 (amd64)
GUI: Bitcoin Knots Qt in a browser-accessible desktop, based on jlesage/baseimage-gui

⁠What is this?

An independently packaged Bitcoin Knots desktop node for users who prefer to manage their own Bitcoin verification and wallet interface on their own hardware. The graphical bitcoin-qt application runs inside a Docker container; its desktop is viewed in a web browser.

This project is not affiliated with or endorsed by the Bitcoin Knots developers. Knots binaries are obtained from the official Bitcoin Knots website. Bitcoin Knots transaction-relay policy does not remove confirmed transactions from the blockchain or dramatically reduce archival disk requirements.

The Docker image contains application software only. Blockchain databases, wallet files and settings must live in persistent storage outside the image.

⁠Pull

After the image is successfully published:

docker pull bmmbmm01/bitcoinknotsgui:29.4.3.knots20260508

Use a versioned tag to make upgrades intentional. The latest tag should only be used if explicitly published after testing.

⁠Quick start (Unraid or Linux Docker host)

Create persistent folders first. Replace these sample paths with your actual SSD/HDD mounts, and verify both paths are mounted before launching. Do not apply chmod 777.

Create a private environment file outside your Git repository:

# Example: /root/bitcoin-gui.env  (owner-readable only)
USER_ID=99
GROUP_ID=100
SECURE_CONNECTION=1
WEB_AUTHENTICATION=1
WEB_AUTHENTICATION_USERNAME=bitcoin
WEB_AUTHENTICATION_PASSWORD=REPLACE_WITH_A_LONG_UNIQUE_PASSWORD

Then run:

docker run -d \
  --name bitcoin-gui \
  --restart unless-stopped \
  --stop-timeout 180 \
  --env-file /root/bitcoin-gui.env \
  -p 5800:5800 \
  -v /mnt/user/appdata/bitcoin-gui:/config \
  -v /mnt/disks/bitcoin-blockchain:/blockchain \
  bmmbmm01/bitcoinknotsgui:29.4.3.knots20260508

Open https://YOUR-DOCKER-HOST:5800 only on a trusted LAN or VPN. HTTPS may initially use a self-signed certificate. Do not forward this port from your router or expose the GUI directly to the internet.

The example USER_ID=99 and GROUP_ID=100 are common on Unraid. Use the actual intended account IDs and file ownership on other Linux hosts.

⁠Storage layout

The application defaults to -datadir=/config/.bitcoin. To place block files on the separate disk, add blocksdir=/blockchain to /config/.bitcoin/bitcoin.conf only after confirming the option with the installed release. The blocks subdirectory will be created beneath the configured blocks directory. The chainstate and wallets remain under /config/.bitcoin unless separately configured.

A full archival node requires substantial free space and synchronization time. The image does not enable pruning by default. Your 2 TB SSD can be used for the blockchain, but monitor available capacity.

⁠Exposed services

Public Docker Hub repository ≠ public-facing wallet GUI. The image may be public, but the running wallet interface should remain private.

⁠Wallet and offline security

• Prefer a watch-only wallet with offline or hardware-device signing for substantial long-term funds.
• Never put seed phrases, private keys, RPC passwords, wallet databases or recovery information in a Dockerfile, Docker image, Git repository or public issue.
• Encrypt and securely back up wallet/recovery data separately from the node's blockchain.
• Use a strong browser password and protect the host and persistent volumes.
• Allow time for a clean shutdown before unplugging or moving a blockchain disk.
• A stopped container can be restarted later; the node must synchronize blocks missed while offline.
• Image downloads are not a substitute for verifying Bitcoin Knots release signatures.

⁠Updating

1. Back up wallet data safely and stop the running container.
2. Verify the exact upstream Bitcoin Knots release and its signatures.
3. Pull the new versioned image once published.
4. Recreate the container using the same persistent volume mounts.
5. Verify wallet functionality, synchronization and logs before treating the upgrade as complete.

The project intentionally avoids silent automatic upgrades of wallet/node software.

⁠Support and references

• Docker Hub — bmmbmm01/bitcoinknotsgui⁠
• Official Bitcoin Knots website⁠
• Bitcoin Knots GitHub⁠
• jlesage GUI base image⁠

The source repository is private. The public Docker Hub description is maintained separately in DOCKERHUB_README.md.

Disclaimer: Self-custody carries a risk of perman