Containerize Server #21

New Issue

sarah · 2018-05-29T21:04:38Z

sarah commented

2018-05-29 21:04:38 +00:00

No description provided.

GBHC commented

2018-10-10 22:04:56 +00:00

As a first pass there is this branch in my fork https://git.openprivacy.ca/GBHC/cwtch/src/21ContainerizeServer

This is a multistage container, the first copies cwtch into a golang container, pulls down the dependencies, compiles it and makes it available to the second stage.

The second stage relies on this image ( https://gitlab.com/ablative-hosting/containedonion/blob/master/Dockerfile - which could instead be another build step within this Dockerfile), it overrides the torrc so it'll work with a locally running cwtch (ControlSocket and cookies etc instead of ControlPort and Hash) and overrides the entry point to daemonise tor and then launch cwtch after 15 seconds (to allow tor time to bootstrap and bring up its ports).

To test;
docker build --no-cache -t cwtch .
docker run cwtch:latest

Currently responds with;
2018/10/10 21:52:56 starting cwtch server...
2018/10/10 21:52:56 using local port: 27492
2018/10/10 21:52:56 running a descriptor check because you are on tor version < 0.3.5.1-alpha. this will take a little while but only happens once per tor process--onion service pair
2018/10/10 21:53:11 cwtch server running on cwtch:dkk3ravvvdd47jr7qfd5hip7vlb22nitqqgux3dx4dsc6snqcrmgcfid.onion:9878
2018/10/10 21:53:12 There was an error

But haven't had chance to dig deeper into whether this is a problem with the container or just this version of Tor/Cwtch

As a first pass there is this branch in my fork https://git.openprivacy.ca/GBHC/cwtch/src/21ContainerizeServer This is a multistage container, the first copies cwtch into a golang container, pulls down the dependencies, compiles it and makes it available to the second stage. The second stage relies on this image _( https://gitlab.com/ablative-hosting/containedonion/blob/master/Dockerfile - which could instead be another build step within this Dockerfile)_, it overrides the torrc so it'll work with a locally running cwtch _(ControlSocket and cookies etc instead of ControlPort and Hash)_ and overrides the entry point to daemonise tor and then launch cwtch after 15 seconds (to allow tor time to bootstrap and bring up its ports). To test; docker build --no-cache -t cwtch . docker run cwtch:latest Currently responds with; 2018/10/10 21:52:56 starting cwtch server... 2018/10/10 21:52:56 using local port: 27492 2018/10/10 21:52:56 running a descriptor check because you are on tor version < 0.3.5.1-alpha. this will take a little while but only happens once per tor process--onion service pair 2018/10/10 21:53:11 cwtch server running on cwtch:dkk3ravvvdd47jr7qfd5hip7vlb22nitqqgux3dx4dsc6snqcrmgcfid.onion:9878 2018/10/10 21:53:12 There was an error But haven't had chance to dig deeper into whether this is a problem with the container or just this version of Tor/Cwtch

sarah commented

2018-10-10 22:19:45 +00:00

This is Awesome!

The error is likely related to some workarounds @erinn has been implementing to cope with issues with older versions of tor (see openprivacy/asaur#1 for more information)

This is Awesome! The error is likely related to some workarounds @erinn has been implementing to cope with issues with older versions of tor (see https://git.openprivacy.ca/openprivacy/asaur/pulls/1 for more information)

dan commented

2018-10-10 22:23:52 +00:00

I am working on getting a brand new 0.5.2-alpha version of tor statically compiled and commited to openpriv/buildfiles. Right now the 0.3.3.7 is too old. Dunno if that'll help?

erinn commented

2018-10-11 00:27:47 +00:00

opened #141 - yes, that output is my fault. it is all just informational, everything looks good in that output to me

GBHC commented

2018-10-15 12:10:18 +00:00

Pull Request: #145

Pull Request: https://git.openprivacy.ca/cwtch.im/cwtch/pulls/145

dan commented

2018-10-17 23:40:39 +00:00

merged
still out standing:

I'd suggest that once I've added the README changes someone at OpenPrivacy signup to Docker Hub and configure Drone to push the image there ( http://docs.drone.io/publish-docker-images/ seems to be lacking :/ ), once there's a "public" image available I can submit another PR with a k8s manifest?
In order for a kubernetes manifest to be useful we need to know where to pull the image(s) from.

I'll dig into this! :)

Great progress and thanks!

merged still out standing: - I'd suggest that once I've added the README changes someone at OpenPrivacy signup to Docker Hub and configure Drone to push the image there ( http://docs.drone.io/publish-docker-images/ seems to be lacking :/ ), once there's a "public" image available I can submit another PR with a k8s manifest? - In order for a kubernetes manifest to be useful we need to know where to pull the image(s) from. I'll dig into this! :) Great progress and thanks!

erinn referenced this issue from a commit

2018-10-22 23:12:33 +00:00

Closes #21...

erinn closed this issue

2018-10-22 23:12:33 +00:00

sarah reopened this issue

2018-10-22 23:15:14 +00:00

erinn closed this issue

2018-10-27 09:00:09 +00:00

Sign in to join this conversation.