did:onion in Docker images

[clehner]

Our did:onion implementation (#125) expects a local SOCKS5h proxy at 127.0.0.1:9050. In the Docker images this is not available. Should the Docker images be updated to include Tor? Or should users of the Docker image be expected to bring their own Tor if they want to use did:onion? Should there be a CLI option, env var, and/or resolution input option for the Tor proxy host/port/URL for did:onion to use instead of socks5h://127.0.0.1:9050?

[clehner]

Maybe, for Universal Resolver (#138), a separate Tor docker container could be added in docker-compose.yml, using a bridget network shared with the DIDKit container. Then DIDKit could access the local Tor proxy.

Or, maybe port forwarding could be used instead of a bridged network; DIDKit would then need to be updated to make the Tor proxy URL configurable (e.g. using an environmental variable) so that it could use the proxy in the other container.