-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev: add tor from repo to standalone #47
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested this as described in joinmarket-webui/jam#396.
Both a scheduler round on instance A (the dev regtest build) with instance B (the standalone regtest build) as a maker and a single coinjoin on instance B with instance A as a maker worked.
I don't know anything about configuring Tor, though. So I can only acknowledge that everything worked on my machine (in regtest).
Thank you @dnlggr 👍 |
Same as dnlggr, I don't know much about this. Changeset looks good to me, though. |
Closes #43.
This PR adds Tor to the
standalone
image.Before this PR, an external container has been necessary to connect to IRC or to the directory nodes.
After this PR is applied, the image lives up to its name and is truly "standalone", meaning: No external dependencies. A Tor daemon will be started at the startup of the container.
The changes in this PR are up to debate and every input or suggestion is highly appreciated.
How to test?
This PR can be tested by following the instructions in joinmarket-webui/#396 . A build of this branch has been made available as docker image, which is extended by the secondary container in the regtest setup.
Addendum
Previous attempts included installing Tor from source via flag
--with-local-tor
of joinmarket'sinstall.sh
script.This has been working great locally, but led to longer build times on GitHub's environment (from ~40min to up to ~2h(!)) and subsequently failing at the unit tests for Tor ([1], [2], [3]). Installing it from an official repository (via
apt-get
) is a compromise between ease of use and robustness. Before, it was relied upon an external container, where the sources where also "unknown", or, as e.g. in Umbrels case, totally outside of the users control. It is always possible for a user to switch to another instance by adapting and passing configuration variables.