Breaking change upcoming in v1.5
To maintain best security practices, we're changing the user:group on the Docker container to besu.
What this means for you:
- If you are running Besu as a binary, there is no impact.
- If you are running Besu as a Docker container and have a volume mount for data, ensure that the
permissions on the directory allow other users and groups to r/w. Ideally this should be set to
besu:besuas the owner.
Note that the besu user only exists within the container not outside it. The same user ID may match
a different user outside the image.
If you’re mounting local folders, it is best to set the user via the Docker —user argument. Use the
UID because the username may not exist inside the docker container. Ensure the directory being mounted
is owned by that user.
Upcoming 1.5 release
The 1.5 release is scheduled for early July.
1.4.6
Additions and Improvements
- Print node address on startup. #938
- Transaction pool: price bump replacement mechanism configurable through CLI. #928 #930
Bug Fixes
- Added timeout to queries. #986
- Fixed issue where networks using onchain permissioning could stall when the bootnodes were not validators. #969
- Update getForks method to ignore ClassicForkBlock chain parameter to fix issue with ETC syncing. #1014
Known Issues
Known issues are open issues categorized as Very High or High impact.
Previously identified known issues
- Scope of logs query causing Besu to hang
- Eth/65 loses peers
- Fast sync when running Besu on cloud providers
- Privacy users with private transactions created using v1.3.4 or earlier