+1 The jar can be build and made available as a nightly/dev artifact for quick development and testing purposes for convenience.
Then provide the one liner command to get up and running, assuming jre and docker is present :-) The jar can’t and should not be distributed as part of an Apache release. - Carlos Santana @csantanapr > On Nov 13, 2019, at 8:55 AM, Michele Sciabarra <[email protected]> wrote: > > I did some experimentations with the docker in docker and ultimately I am > convinced it is actually better just to use the jar. I would then suggest to > distribute at least the precompiled jar instead of requiring to compile by > himself. > > -- > Michele Sciabarra > [email protected] > > ----- Original message ----- > From: Chetan Mehrotra <[email protected]> > To: [email protected] > Subject: Re: OpenWhisk as a single docker image? > Date: Wednesday, November 13, 2019 6:00 AM > > Running standalone logic within a Docker would be tricky as there is quite > a bit of logic involved to use the right IP for inter docker communications > specially in Kafka and Api Gateway part. > > Hence currently we expect that to use standalone the user has at minimum > JDK + Docker on the host > > Chetan Mehrotra > > >> On Tue, Nov 12, 2019 at 10:58 PM Matt Sicker <[email protected]> wrote: >> >> Docker in Docker has some slight security improvements depending on >> your use case, too, compared to just mounting your docker socket into >> the running container. >> >>> On Sat, 9 Nov 2019 at 10:30, Tyson Norris <[email protected]> >>> wrote: >>> >>> 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 >> https://github.com/apache/openwhisk/blob/231e739373ef681c44b5647a6956d5838a87db2e/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/docker/StandaloneDockerContainerFactory.scala#L37 >>> 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. >>> >>> Tyson >>> >>> On 11/9/19, 5:38 AM, "Michele Sciabarra" <[email protected]> wrote: >>> >>> Wow. I missed those evolutions. So I guess it should not be hard to >> package it as a docker image. >>> >>> To be able to say to people: execute "docker run -p 8080:8080 >> openwhisk/standalone" and enjoy... >>> >>> 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 >>> [email protected] >>> >>> ----- Original message ----- >>> From: Rodric Rabbah <[email protected]> >>> To: [email protected] >>> Subject: Re: OpenWhisk as a single docker image? >>> Date: Saturday, November 09, 2019 2:31 PM >>> >>> Do you mean the standalone controller? >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fopenwhisk%2Fblob%2Fmaster%2Fcore%2Fstandalone%2FREADME.md&data=02%7C01%7Ctnorris%40adobe.com%7Cfc313c39337a44a5882a08d7651a0cbc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637089034867332217&sdata=OCnWo8R5OfbKLaSQCEeI%2B7pqz0ewp%2BYQGBK2msMoMtc%3D&reserved=0 >>> >>> -r >>> >>>> On Nov 9, 2019, at 8:18 AM, Michele Sciabarra < >> [email protected]> 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 >>>> [email protected] >>> >>> >> >> >> -- >> Matt Sicker <[email protected]> >>
