Skip to content
You are reading Hyperledger Besu development version documentation and some displayed features may not be available in the stable release. You can switch to stable version using the version box at screen bottom.

Updated on March 1, 2020

Migrating from pre-1.2 Docker image to 1.2+

Before v1.2

The Hyperledger Besu Docker image had an entry-script that automatically added options to the Besu command line. You could not set the options using command line arguments.

The options automatically added to the Besu command line for the Besu Docker image before v1.2 were:

The --node-private-key-file command line option was not available and the node key was always read from the data path.

From v1.2

All file options (for example, --config-file) no longer have a default. Add the relevant command line options to your Besu command line and specify the file path.

The --data-path default is now /opt/besu.

The --node-private-key-file default is now /opt/besu/key.

Important

Do not mount a volume at the default data path (/opt/besu). Mounting a volume at the default data path interferes with the operation of Besu and prevents Besu from safely launching.

To run a node that maintains the node state (key and database), --data-path must be set to a location other than /opt/besu and a storage volume mounted at that location.

The host and port options continue to default to the previously set values.

Tip

You can set all command line options using environment variables.

Questions or feedback? You can discuss issues and obtain free support on Hyperledger Besu chat channel.
For Hyperledger Besu community support, contact the mailing list besu@lists.hyperledger.org