Hi Carlos Thanks. Yes, there seems to be a mismatch, hence https://github.com/openwhisk/openwhisk-devtools/issues/4
Whatever we do going forward — keep the current Consul based setup (all but devtools) or move to simple properties file (devtools) — I think we should make sure to have a consistent setup working out-of-the-box for quick/simple testing. Thanks Felix Am 27.01.2017 um 02:57 schrieb Carlos Santana <[email protected]<mailto:[email protected]>>: Hi Felix I didn't want to leave this email thread hanging out here as unresponsive from the community. It looks like you got it working following Vagrant flow from the main repo. I think there was a recent change around setting up keys on deployment that it's currently handle in all installation methods (mac, ubuntu, vagrant, Travis ) but maybe is not reflected on docker-compose flow in the dev tools repo. -- Carlos On Wed, Jan 25, 2017 at 5:19 AM Felix Meschberger <[email protected]<mailto:[email protected]>> wrote: Hi digging along it looks like the OpenWhisk controller is actually not starting. Where the log file then says: [2017-01-24T18:08:18.043Z] [INFO] [??] [WhiskConfig] reading properties from consul at consul.docker:8500 [2017-01-24T18:08:20.989Z] [WARN] [??] [WhiskConfig] failed to read properties from consul: null [2017-01-24T18:08:21.011Z] [ERROR] [??] [Config] required property whisk.system.key still not set Woot ! No properties from consul. I think this is fine, right ? But where do I get the whisk.system.key ? Thanks Felix Am 24.01.2017 um 16:02 schrieb Felix Meschberger <[email protected]<mailto:[email protected]>>: Hi I am trying to run the docker-compose setup of the openwhisk/openwhisk-devtools repository. It builds fine and starts launching the containers. But it waits indefinitely for the openwhisk controller to start while consul fails to connect to port 8888: 2017/01/24 15:01:15 [WARN] agent: http request failed ' http://172.18.0.9:8888/ping': Get http://172.18.0.9:8888/ping: dial tcp 172.18.0.9:8888: getsockopt: connection refused I am running on macOS Sierra with Docker 1.13.0. Could it be docker on mac being the problem ? Thanks Felix
