Private network with Docker tutorial creates network without amendments enabled

[mDuo13]

The private network created by following the Run a Private Network with Docker tutorial uses the default settings for a new network—unfortunately, the default settings are not very useful and they come with no amendments enabled by default. They may eventually converge on voting for anything that has a default vote of yes, but it's probably still not what you want for testing.

One solution is for the rippled.cfg file to include a (long) list of amendments to enable based on what's enabled on Mainnet at the moment, using the (technically deprecated) [amendments] stanza. That might be more practical than trying to figure out how to do a bootstrapping process involving --start, a custom ledger file, or expedited amendment voting.

Similarly, but more easily fixed, the default fee values also use the hard-coded defaults instead of values that match what's on Mainnet now. The fix for this one is to add a fee voting stanza to the rippled.cfg file:

[voting]
reference_fee = 10
account_reserve = 1000000
owner_reserve = 200000

(Those values match Mainnet at time of writing, 2026-01-16.)

For scripts that can easily report on the status of these network settings, see https://github.com/XRPLF/xrpl-docs-data-scripts