Skip to content
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

Hardcoded /var/lib/tor #49

Open
AnotherDroog opened this issue Aug 23, 2019 · 8 comments
Open

Hardcoded /var/lib/tor #49

AnotherDroog opened this issue Aug 23, 2019 · 8 comments

Comments

@AnotherDroog
Copy link
Member

Encountering this on Mac when /var/lib/tor is not created and shared.

ERROR: for neutrino_lnd_1  Cannot start service lnd: b'Mounts denied: \r\nThe path /var/lib/tor\r\nis not shared from OS X and is not known to Docker.\r\nYou can configure shared paths from Docker -> Preferences... -> File Sharing.\r\nSee https://docs.docker.com/docker-for-mac/osxfs/#namespaces for more info.\r\n.'

sudo mkdir /var/lib/tor and adding the dir to shares in Docker fixes it but is tedious for users

@nolim1t
Copy link
Member

nolim1t commented Aug 25, 2019

The docker image doesnt require this mount. Only for a specific compose file which is not in this repo

@AnotherDroog
Copy link
Member Author

Ok, thanks!

Can you move the issue to Noma?

@nolim1t nolim1t transferred this issue from lncm/docker-lnd Sep 12, 2019
@nolim1t
Copy link
Member

nolim1t commented Sep 12, 2019

Moved to NOMA

@nolim1t
Copy link
Member

nolim1t commented Sep 12, 2019

the Mac Tor directory is /usr/local/var/lib/tor, so perhaps a detect for the OS or directory before startup and a quick sed script to rewrite the tor pathname in the compose file might work

@nolim1t
Copy link
Member

nolim1t commented Sep 12, 2019

Although there is some other issues on Macs where we should probably not use docker because Mac support for docker uses a linux VM so there is issues with the container communicating with the tor host.

@AnotherDroog
Copy link
Member Author

I'm thinking vagrant is a solid choice for Mac development. We can do setup of virtualbox VM's as well as docker orchestration with it, i.e. setting up docker to be ready for our compose files.

Instead of messing with the tor path, can't we put it in a container instead?

@nolim1t
Copy link
Member

nolim1t commented Sep 25, 2019

if you can get tor as a container then why not.

Building it isn't the easiest, let alone getting it a multiplatform binary

@AnotherDroog
Copy link
Member Author

I‘m going to focus on containerizing Noma first since that brings the greatest benefit to reducing deployment time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants