DAppNode: Sometimes nginx can not connect to ws backend after updating

[TripleSpeeder]

Observed behaviour: Sometimes after re-installing or updating the node package there are errors in the web service logs that indicate nginx can not connect to the profile service running in the ws container. According to the logs, the web service tries to connect to ws at its previous IP-address.

Workaround: Restart the web service. After restart it connects to the correct IP-address.

Possible solution: Currently all brightID-node services connect to the default docker network of dappnode. We should create a dedicated virtual network for the brightid-node services. Within this network DNS resolution should work correctly.

[TripleSpeeder]

Currently DAppNode does not support additional networks. We need to wait for https://github.com/dappnode/DNP_DAPPMANAGER/issues/618 to be implemented.

[dapplion]

@TripleSpeeder issue done :heart: . Please watch this release to include it https://github.com/dappnode/DNP_DAPPMANAGER/milestone/6