Ok, I will try to build the controller image and see. Will keep you posted.

On 3/2/18, 2:39 PM, "Tyson Norris" <tnor...@adobe.com.INVALID> wrote:

    Thanks Carlos - I think you’re right. 
    Kumar you can either build the controller image with that PR, or else you 
should be able to manually set the docker cmd, e.g. /bin/sh -c \"exec /init.sh 
0 >> /dev/stdout\” on the dcos service for controller; 
    I think you will have similar issue with invoker, mostly because this 
universe is far out of date from current openwhisk images. 
    For invoker can you use the docker cmd as /bin/sh -c \"exec /init.sh --name 
$LIBPROCESS_IP >> /dev/stdout\”
    Additionally, the env vars (both invoker and controller) have changed 
substantially, so I would expect a few hiccups there as well. 
    We are working on getting updates to the universe so that our internal 
deployment details are not included, and it will actually work with recent 
openwhisk images (and stay working) but haven’t gotten everything set just yet. 
    Hope that helps
    > On Mar 2, 2018, at 2:21 PM, Carlos Santana <csantan...@gmail.com> wrote:
    > Maybe for the init.sh this PR is related
    > On Fri, Mar 2, 2018 at 5:09 PM Tyson Norris <tnor...@adobe.com.invalid>
    > wrote:
    >> Check your marathon/dcos service config to verify what image is used, and
    >> that you have the latest image pulled?
    >> The default should be openwhisk/controller - but I see that universe
    >> package marathon config is not set to force pull, so if you are using 
    >> image, make sure you have pulled the latest manually (or change the 
    >> to force pull in dcos/marathon ui).
    >> Tyson
    >>> On Mar 2, 2018, at 12:45 PM, Kumar Subramanian <kumarsubr...@vmware.com>
    >> wrote:
    >>> Hi,
    >>> I have installed the following in DCOS successfully:
    >>> 1. Apigateway
    >>> 2. Exhibitor-dcos
    >>> 3. Kafka (name given is mykafka at the time of installation)
    >>> 4. Whisk-couchdb
    >>> 5. Consul
    >>> 6. Registrator
    >>> Eror when deploying Whisk-Controller in DCOS:
    >>> When I tried to deploy whisk-controller with default settings, then the
    >> service fails to deploy (it just kills and redploys the service
    >> continuously on its own when deploying)
    >>> Here is the content in the Error and Output
    >>> STDERR:
    >>> I0302 20:38:35.176177 19822 exec.cpp:162] Version: 1.2.3
    >>> I0302 20:38:35.180703 19824 exec.cpp:237] Executor registered on agent
    >> 995020e0-5129-44a3-8cf4-65900838b3af-S6
    >>> docker: Error response from daemon: Container command 'init.sh' not
    >> found or does not exist..
    >>> OUTPUT:
    >>> Registered docker executor on
    >>> Starting task whisk-controller.adb62c44-1e59-11e8-8754-3afdc003616b
    >>> Can you please provide your valuable inputs on how to get
    >> whisk-controller deployed in dcos?
    >>> Thanks,
    >>> Kumar.

Reply via email to