openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tyson Norris <>
Subject Re: OpenWhisk as a single docker image?
Date Sat, 09 Nov 2019 16:29:45 GMT
I suspect that due to Docker-in-Docker scenario, it will be easier to use java+jar (+local
docker) instead of running the jar in a container. 

Today you can start the jar with only java <jar>, but you will need a bunch of parameters
(probably different per OS?) to run it in a container, I think.
Local docker client is switched per OS here
I guess this wouldn't apply if running in a container, but it arguably makes running the jar
simpler than running the container IMHO.
I also suspect you won't get the behavior of launching playground ui to browser either, which
I would miss. 


´╗┐On 11/9/19, 5:38 AM, "Michele Sciabarra" <> wrote:

    Wow. I missed those evolutions. So I guess it should not be hard to package it as a docker
    To be able to say to people: execute "docker run -p 8080:8080 openwhisk/standalone" and
    If it is possible I can volounteer to write the dockerfile do that...
    I have a question: does it use the local docker? Where is the invoker?
      Michele Sciabarra
    ----- Original message -----
    From: Rodric Rabbah <>
    Subject: Re: OpenWhisk as a single docker image?
    Date: Saturday, November 09, 2019 2:31 PM
    Do you mean the standalone controller?;;sdata=OCnWo8R5OfbKLaSQCEeI%2B7pqz0ewp%2BYQGBK2msMoMtc%3D&amp;reserved=0
    > On Nov 9, 2019, at 8:18 AM, Michele Sciabarra <> wrote:
    > Hello all, 
    > I remember the discussion about the openwhisk as a single executable that includes
also Kafka. So I wonder: is it now possible to run (for development purposes of course) OpenWhisk
as single docker image if we add also couchdb to that one? Because I have an use case where
even a docker-compose can be inconvenient...
    > -- 
    >  Michele Sciabarra

View raw message