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 consist
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
To circle back: This looks like missing configuration in Consul in the docker
compose setup.
Reported https://github.com/openwhisk/openwhisk-devtools/issues/4
(Note: This of course ties back into the discussion about whether we use Consul
at all or not, see [1])
Thanks
Felix
[1]
https://list
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
>
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 :
> 2017/01/24 15:01:15 [WARN] agent: ht
