Unable to run CI example (permission denied)

[Thegaram]

Unable to run CI example (permission denied)

[talex5]

Did you already run make in that directory? Maybe you already have a _build directory owned by a different user? If not, try changing the chown command in the Dockerfile to chown -R and see if that helps...

[talex5]

Actually, I think this example is just broken. Could you try the fix in #619?

[Thegaram]

Yep, it works now. Thanks for the quick fix @talex5!

[Thegaram]

The way I'm trying to run the CI example:

1. Run DataKit server

$ docker run -it --net datakit-net --name datakit -v [path_to_git_repo]:/data -p 5640:5640 datakit/db

2. Check server by running DataKit client

$ docker run -it --privileged --net datakit-net datakit/client
bash-4.3$ ls -l /db/branch/master/ro/
[git_repos_contents]

From this, and the subsequent server logs, I assume that the server is running and reachable on tcp://0.0.0.0:5640.

3. Run CI

$ docker run --name my-ci --net datakit-net -p 8443:8443 my-ci --metadata-store tcp:0.0.0.0:5640
2018-03-02 13:12.13 INF [datakit-ci] Generating new private key...
2018-03-02 13:12.13 APP [datakit-ci] >>> Configure the CI by visiting
                                     https://127.0.0.1:8443/auth/intro/SFEq6uYvHCgKJjg1iOrHy4BwIG2heYGc
2018-03-02 13:12.13 INF [datakit-ci] Connecting to DataKit server on tcp:0.0.0.0:5640
2018-03-02 13:12.13 INF [datakit-ci] Starting monitor loop
2018-03-02 13:12.13 WRN [datakit-ci] Failed to connect to DataKit: (Failure
   "Failed to connect to DataKit server at proto=\"tcp\" addr=\"0.0.0.0:5640\": (Failure\
  \n  \"Error connecting socket to 9p endpoint tcp:0.0.0.0:5640: Unix.Unix_error(Unix.ECONNREFUSED, \\\"connect\\\", \\\"\\\")\")") (will retry in 10s)

Could you please point out what I'm doing wrong? (I would create a new issue but I assume this is due to some misconfiguration on my side.)

[Thegaram]

Okay, it seems like the CI can connect if I use 172.19.0.2:5640 (taken from the output of docker network inspect datakit-net).

[talex5]

You have to give the actual address of the server. 0.0.0.0 is a special address that means "listen on any interface", but you can't use it as a destination. You should be able to use --metadata-store tcp:datakit:5640.

[Thegaram]

Yeah, it works with tcp:datakit:5640, thanks!