Docker - Duniter wrapper + Entrypoint can survive a config / peers.db loss

Duniter wrapper

/usr/bin/duniter is a script again which does the very minimum so that the duniter command can work from anywhere and without and with --home parameter. the default Duniter home is /var/lib/duniter, but a different one can be set with --home <new_home>.

Survive a config loss

When conf.json is not found and a peer node is defined as DUNITER_SYNC_HOST or DUNITER_PEER_HOST, bootstrap a new conf.json file with the blockchain parameters from this node.

This is enough for duniter to survive a config loss with no need for a full resync.

Survive a peers.db loss

When peers.db is not found and a peer node is defined as DUNITER_SYNC_HOST or DUNITER_PEER_HOST, bootstrap a new peers database using sync --only-peers against this node.

Auto sync against a chunks folder

It is now possible to autosync against a chunks folder from a dex export. It only needs these settings:

• DUNITER_AUTO_SYNC=true
• DUNITER_SYNC_HOST=<path_to_chunks_folder>
• DUNITER_PEER_HOST=<node_to_get_peers_from>

doc/use/docker.md

@@ -35,7 +35,7 @@ Restart the stopped node:
 
 ### Volumes
 
-The container creates 2 docker volumes. The first one is mounted under `/etc/duniter` and contains the Duniter configuration. The other one is mounted under the Duniter home directory, i.e. `/var/lib/duniter`. This is the place the Duniter database will be stored.
+The container creates 2 docker volumes. The first one is mounted under the Duniter home directory, i.e. `/var/lib/duniter`. This is the place the Duniter configuration files and database will be stored. The other one is mounted under `/etc/duniter` which is where it is recommended to store the keyfile when the instance is a member node, so that the keyfile is kept separated from the - potentially - volatile data.
 
 See more about managing volumes with docker in the [docker documentation](https://docs.docker.com/storage/volumes/).