Skip to content

Introduced docker integration - #46

Merged
Roasbeef merged 3 commits into
lightninglabs:masterfrom
OpinionatedGeek:master
May 18, 2019
Merged

Introduced docker integration#46
Roasbeef merged 3 commits into
lightninglabs:masterfrom
OpinionatedGeek:master

Conversation

@OpinionatedGeek

@OpinionatedGeek OpinionatedGeek commented Apr 18, 2019

Copy link
Copy Markdown
Contributor

Introduced docker integration:

  • Added Dockerfile to build loopd and loop with no dependencies.
  • Added instructions to build and run docker image.

There's no MAINTAINER tag in the Dockerfile (yet). I wasn't sure who to put. Much of the Dockerfile contents come from @Roasbeef's LND Dockerfile though.

I don't know if the tone of the instructions is OK. Any thoughts?

Fixes #43.

* Added Dockerfile to build loopd and loop with no dependencies.
* Added instructions to build and run docker image.
@alexbosworth

Copy link
Copy Markdown
Member

looks good to me, although I'm not yet a Docker user

@tdickman tdickman left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for making this - left 1 comment, but everything else looks good to me. Thank you for the thorough documentation.

Comment thread DOCKER.md Outdated

One way of running `loopd` is
```
docker run --rm -it --name loopd -v $HOME/.lnd:/root/.lnd loop:latest loopd --network=testnet --lnd.host <my-lnd-ip-address>:10009

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably worth mapping the ~/.loopd directory as well since it stores the state of active loops.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent point! Thanks for that. I've updated that line to map ~/.loop, as well as added a note about why.

Geoff Taylor added 2 commits April 18, 2019 21:35
* Would have caused problems because ~/.loop wasn't mapped
* Now map entire home directory
* Removed mapping of home directory - one of the benefits of docker is being explicit about the resources the container uses so I felt bad mapping the entire home directory when only two known folders were used.

@tdickman tdickman left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (not sure I have the permissions to approve it though 😄 ).

@Roasbeef Roasbeef left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM ✈️

@Roasbeef
Roasbeef merged commit 793fb4d into lightninglabs:master May 18, 2019
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

Successfully merging this pull request may close these issues.

'x509: certificate signed by unknown authority' when running in Docker container

4 participants