bitcoin-docker's Introduction

bitcoin-docker

Container to run Bitcoin Core in full or pruned mode.

Synopsis

This container can be used to run Bitcoin Core in either an external mode or in an internal (pruned) mode. Containers in external mode synchronize with the Bitcoin network and broadcast transactions from internal mode containers. Containers in internal mode are isolated from the public internet and communicate over an internal network with external mode containers. The goal is to make wallets safer by keeping them isolated from the public internet.

Configuration

Environment variable	Description
`EXTERNAL_PEER`	Hostname of an external mode container that an internal mode container should connect to.
`RPC_USERNAME`	Username for RPC authentication.
`RPC_PASSWORD`	Password for RPC authentication.
`WEBHOOK_ENDPOINT`	Endpoint to receive JSON POST requests of Bitcoin Core notifications.
`FORWARD_BITCOIN_RPC_PORT`	Public port to the Bitcoin Core RPC server.

Development

Preparation

Start by cloning this repository to your machine
Copy the .env.example file to .env and configure it.

Commands

Setup

Build the application. It will copy the .env.example file to .env if it could not be found.

make setup

Up

Start the application.

make up

Down

Stop the application.

make down

Shell

Interact with the application.

make shell

Attribution

Bitcoin Core (License)

bitcoin-docker's People

Contributors

Watchers

bitcoin-docker's Issues

Move chainstate directory to local volume

Recover from "Corrupted block database detected"

This was observed on a pruned node during initial syncing of the chain.

2023-12-29T23:45:53Z init message: Verifying blocks…
2023-12-29T23:45:53Z Verifying last 6 blocks at level 3
2023-12-29T23:45:53Z Verification progress: 0%
2023-12-29T23:45:53Z Verification error: found bad block at 1179543, hash=00000000000001db83fa16981d1d69a16910e632f48318e34deb8fdcf0565ac9 (bad-txnmrklroot, hashMerkleRoot mismatch)
2023-12-29T23:45:53Z : Corrupted block database detected.
Please restart with -reindex or -reindex-chainstate to recover.
2023-12-29T23:45:53Z Aborted block database rebuild. Exiting.
2023-12-29T23:45:53Z Shutdown: In progress...
2023-12-29T23:45:53Z scheduler thread exit
2023-12-29T23:45:53Z Flushed fee estimates to fee_estimates.dat.
2023-12-29T23:45:53Z Fatal LevelDB error: Corruption: not an sstable (bad magic number)
2023-12-29T23:45:53Z You can use -debug=leveldb to get more complete diagnostic messages
2023-12-29T23:45:53Z *** System error while flushing: Fatal LevelDB error: Corruption: not an sstable (bad magic number)
2023-12-29T23:45:53Z Error: A fatal internal error occurred, see debug.log for details
2023-12-29T23:45:53Z ForceFlushStateToDisk: failed to flush state (System error while flushing: Fatal LevelDB error: Corruption: not an sstable (bad magic number))
2023-12-29T23:45:53Z Fatal LevelDB error: Corruption: not an sstable (bad magic number)
2023-12-29T23:45:53Z You can use -debug=leveldb to get more complete diagnostic messages
2023-12-29T23:45:53Z *** System error while flushing: Fatal LevelDB error: Corruption: not an sstable (bad magic number)
2023-12-29T23:45:53Z Error: A fatal internal error occurred, see debug.log for details
2023-12-29T23:45:53Z ForceFlushStateToDisk: failed to flush state (System error while flushing: Fatal LevelDB error: Corruption: not an sstable (bad magic number))
2023-12-29T23:45:57Z Shutdown: done

Recommend Projects