Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 147AA200BDB for ; Mon, 12 Dec 2016 17:46:25 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 132E7160B22; Mon, 12 Dec 2016 16:46:25 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B42ED160B1A for ; Mon, 12 Dec 2016 17:46:23 +0100 (CET) Received: (qmail 14659 invoked by uid 500); 12 Dec 2016 16:46:22 -0000 Mailing-List: contact users-help@groovy.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@groovy.apache.org Delivered-To: mailing list users@groovy.apache.org Received: (qmail 14649 invoked by uid 99); 12 Dec 2016 16:46:22 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Dec 2016 16:46:22 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 56B8B1AA23E for ; Mon, 12 Dec 2016 16:46:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.379 X-Spam-Level: ** X-Spam-Status: No, score=2.379 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id w8CXc5jWXz6U for ; Mon, 12 Dec 2016 16:46:18 +0000 (UTC) Received: from mail-qk0-f177.google.com (mail-qk0-f177.google.com [209.85.220.177]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 90F715FD23 for ; Mon, 12 Dec 2016 16:46:18 +0000 (UTC) Received: by mail-qk0-f177.google.com with SMTP id q130so88656007qke.1 for ; Mon, 12 Dec 2016 08:46:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=3WCm2EKZjDmEq8Puj2iPUXttW8UNp/yNv4nrzLkQUoc=; b=EB3cZmYFKVb1Ee8BRN7r4WU3hXf6OHvxFyRUIC/Ie16gjhfUc+ML91InfpdjhNpHBN ngGhORndr3D4HftLHHwb2CVkcE3Qw6Gij3kxfT9qBYrvfqUaNq7dYqRM4Iy4Aq6oaIH1 /Q8Y0mFPSNRCSyxkUlysfAKWpZyAQicmIO1WFdQQRV3x1O9qRbskhSX84ncA9a5AJFt9 9xDWEKSvlNYGUVyUTAg156vpRYdQr+pN+NgX0ImuFa7BpBJwnM6Yw9dLjt4dPIuP5s+j M3gsxp/9ac17XLN8towt9F9ZuxEv5gmUMXEPBanxQ+a4HD2CnDjJV+MvkZWdT2S9V+em PBng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=3WCm2EKZjDmEq8Puj2iPUXttW8UNp/yNv4nrzLkQUoc=; b=Lv7Bral+g/0tkaX/Yyksy5JkKo5f9gkaKLithKzVGlj47aVlJ8QeabblE0NFvytJC4 TRId78wRO/jcxHnHDHKictLqwES95+IAYWMnNcO/YxCH3hr+CNR59lAg+zrPEJXsa713 gRxoUSY8j26wISnbqYyuN2oPKsnEiSZ4TbsYh1Cy2K2oF4ZEOHHytALaRHKeT0NAaeCO zKqhOHfvcKVIL5UyQO8bjJVUaInXh5WfFvxyzdQZ8WUaKcqiFJJ4Sj9Muft3OYcVj7Zi JtLK2TKw2CSRtaBS/PXURjKe6Zclic61lNcSWR/kQLmh7tYhotj02Hr28itzMELlk5JC wC2A== X-Gm-Message-State: AKaTC00zMdW9W5xye4offEhzYV7V01OPLzGfnL916MUvFaGkCjEBE3c6/zGnCwXlwO5SbybEuY4J7dGDZeAQjw== X-Received: by 10.55.221.29 with SMTP id n29mr94670508qki.114.1481561162734; Mon, 12 Dec 2016 08:46:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.84.81 with HTTP; Mon, 12 Dec 2016 08:45:42 -0800 (PST) In-Reply-To: References: From: Keegan Witt Date: Mon, 12 Dec 2016 11:45:42 -0500 Message-ID: Subject: Re: Groovy Docker images To: users@groovy.apache.org Content-Type: multipart/alternative; boundary=001a1149d3a4d1a611054378d6c5 archived-at: Mon, 12 Dec 2016 16:46:25 -0000 --001a1149d3a4d1a611054378d6c5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable It would be nice to be able to offer an Alpine based image. There's quite a size difference. The non-Alpine image is 388.4 MB while the Alpine image is 189 MB, less than 1/2 the size. Do you think we should mount ~/.groovy as a volume? Might be useful for ~/.groovy/grapes in particular. On Sun, Dec 11, 2016 at 5:12 AM, Keegan Witt wrote: > Thanks for the feedback, Thibault. I've responded in-line. > > - Might be better not to start groovysh, might be mentioned in > Dockerfile comments instead > - It's just a default to be run when the user does "docker run", they > can specify an alternative command to run if they choose (see my gr= ape > example further down). Ruby, JRuby, and Python all do this, and it= 's > mentioned in Docker's best practices > > . > - Add Dockerfile comments, at least a link to the repo containing the > dockerfiles > - Did you mean a link to the Docker Hub page? If not, what > comments do you think would be helpful in the Dockerfiles? > - Add a LICENSE file to the github repo > - Good catch. Done. > - Add a travis job to the github repo that verifies the Dockerfiles > - Yea, I intend to change the readme to link to the Docker Hub page > (once published) and a Travis job, as you've suggested. Build auto= mation > is something I have to work out yet, goes with the templating work = I > mentioned. > - Provide one sample image on top of those images with some hello > world application > - Usage is pretty straightforward, but I could do that. It probably > should be in a separate repo though, don't you think? Also any sug= gestions > on a good sample? I was thinking something not compiled Groovy, be= cause > for that you'd just run with Java Docker image, no need for Groovy = on > path. Maybe a script of some kind. > - Check if grapes can be run from containers > - Grape seemed to work, was there a particular problem you were > concerned about? > > $ docker run -it --rm --name groovy groovy:jre8-latest > > Dec 11, 2016 9:37:40 AM java.util.prefs.FileSystemPreferences$1 run > > INFO: Created user preferences directory. > > Groovy Shell (2.4.7, JVM: 1.8.0_111) > > Type ':help' or ':h' for help. > > ------------------------------------------------------------ > ------------------------------------------------------------ > ------------------------------------------------------------ > -------------------------- > > groovy:000> groovy.grape.Grape.grab(group:'org.springframework', > module:'spring', version:'2.5.6') > > =3D=3D=3D> null > > > $ docker run -it --rm --name groovy groovy:jre8-latest grape install > 'org.springframework' 'spring' '2.5.6' > > :: loading settings :: url =3D jar:file:/opt/groovy/lib/ivy-2 > .4.0.jar!/org/apache/ivy/core/settings/ivysettings.xml > > :: resolving dependencies :: caller#all-caller;working72 > > confs: [default] > > found org.springframework#spring;2.5.6 in jcenter > > found commons-logging#commons-logging;1.1.1 in jcenter > > downloading https://jcenter.bintray.com/org/springframework/spring/2.5. > 6/spring-2.5.6.jar ... > > [SUCCESSFUL ] org.springframework#spring;2.5.6!spring.jar (2741ms= ) > > downloading https://jcenter.bintray.com/commons-logging/commons-logging/ > 1.1.1/commons-logging-1.1.1.jar ... > > [SUCCESSFUL ] commons-logging#commons-logging;1.1.1!commons-loggi= ng.jar > (719ms) > > > On Sun, Dec 11, 2016 at 3:32 AM, Thibault Kruse > wrote: > >> Some minor comments: >> - might be better not to start groovysh, might be mentioned in >> Dockerfile comments instead >> - Add Dockerfile comments, at least a link to the repo containing the >> dockerfiles >> - Add a LICENSE file to the github repo >> - Add a travis job to the github repo that verifies the Dockerfiles >> - check if grapes can be run from containers >> - Provide one sample image on top of those images with some hello >> world application >> >> >> On Sun, Dec 11, 2016 at 3:24 PM, Keegan Witt >> wrote: >> > Sorry for the long turnaround on this. I've got some basic Dockerfile= s >> put >> > together: https://github.com/keeganwitt/groovy-docker. Please let me >> know >> > what I can improve. One thing I might do is template out the >> Dockerfiles >> > similar to what Ruby did to make it easier to publish images when >> there's a >> > new Groovy version. >> > >> > I planned on creating both Alpine and non-Alpine images since that >> seems to >> > be the current practice. But we need to get GROOVY-7906 resolved for >> the >> > Alpine images to work. >> > >> > I'm concerned about whether it'd be legal for us to distribute the >> Oracle >> > JDK with Groovy. I saw this article on the topic: >> > http://blog.takipi.com/running-java-on-docker-youre-breaking-the-law/. >> I >> > don't speak legalize though. I haven't seen anyone else (Jruby, etc) >> > publishing Oracle JDK, and Oracle has never published Docker images th= at >> > were not OpenJDK. The only images floating out there have been >> > community-created. So for the time being, I don't plan to publish >> Oracle >> > based images. >> > >> > Once we think these look good, I'll move the repo over to groovy org i= n >> > Github and we'll get them published to Docker Hub. Maybe we could als= o >> ask >> > Apache Infra to get them added to https://hub.docker.com/u/apache/, I >> > haven't decided. What do you think? >> > >> > On Fri, Sep 9, 2016 at 11:19 PM, Corum, Michael >> wrote: >> >> >> >> Not related to Groovy as much. We=E2=80=99ve never been able to get = OpenJDK >> (7 or >> >> 8) to work properly with Oracle JDBC drivers on Alpine. Always have >> to use >> >> Oracle JDK and in the research we did, we found others with the same >> issues. >> >> >> >> Michael Corum >> >> >> >> VP, Technical Architecture Solutions >> >> >> >> >> >> >> >> RGA Reinsurance Company >> >> >> >> 16600 Swingley Ridge Road >> >> >> >> Chesterfield, Missouri 6301701706 >> >> >> >> T 636.736.7066 >> >> >> >> www.rgare.com >> >> >> >> >> >> >> >> >> >> From: Guillaume Laforge >> >> Reply-To: "users@groovy.apache.org" >> >> Date: Friday, September 9, 2016 at 10:16 PM >> >> To: "users@groovy.apache.org" >> >> Subject: Re: Groovy Docker images >> >> >> >> Out of curiosity, what's the problem with OpenJDK? >> >> Is it related to Groovy or not at all? >> >> >> >> On Sat, Sep 10, 2016 at 5:09 AM, Corum, Michael >> wrote: >> >>> >> >>> >> >>> Either one >> >>> Alpine =E2=80=93 I suspect others will want other options though >> >>> Would most definitely prefer Oracle but I assume other would want >> OpenJDK >> >>> as well. For my purposes OpenJDK just doesn=E2=80=99t work at all. >> >>> >> >>> Michael Corum >> >>> >> >>> VP, Technical Architecture Solutions >> >>> >> >>> >> >>> >> >>> RGA Reinsurance Company >> >>> >> >>> 16600 Swingley Ridge Road >> >>> >> >>> Chesterfield, Missouri 6301701706 >> >>> >> >>> T 636.736.7066 >> >>> >> >>> www.rgare.com >> >>> >> >>> >> >>> >> >>> >> >>> From: Keegan Witt >> >>> Reply-To: "users@groovy.apache.org" >> >>> Date: Friday, September 9, 2016 at 9:48 PM >> >>> To: "users@groovy.apache.org" >> >>> Subject: Groovy Docker images >> >>> >> >>> I was thinking of putting together some Docker images for Groovy, wi= th >> >>> the idea they might be useful to base Grails, Gradle, etc images on >> and >> >>> wondered people's opinions on a few things. >> >>> >> >>> Should I install Groovy manually in somewhere like /opt? Or use >> SDKMAN? >> >>> Should I have images based on Alpine and Debian? Alpine only? >> >>> I presume OpenJDK images are fine as bases? Any reason we'd need an >> >>> Oracle based image too? >> >>> >> >>> Thoughts? >> >>> >> >>> -Keegan >> >> >> >> >> >> >> >> >> >> -- >> >> Guillaume Laforge >> >> Apache Groovy committer & PMC Vice-President >> >> Developer Advocate @ Google Cloud Platform >> >> >> >> Blog: http://glaforge.appspot.com/ >> >> Social: @glaforge / Google+ >> > >> > >> > > --001a1149d3a4d1a611054378d6c5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It would be nice to be able to offer an Alpine based image= .=C2=A0 There's quite a size difference.=C2=A0 The non-Alpine image is = 388.4 MB while the Alpine image is 189 MB, less than 1/2 the size.
=
Do you think we should mount ~/.groovy as a volume?=C2=A0 Mi= ght be useful for ~/.groovy/grapes in particular.

On Sun, Dec 11, 2016 at 5:12 AM= , Keegan Witt <keeganwitt@gmail.com> wrote:
Thanks for the feedback, Th= ibault.=C2=A0 I've responded in-line.
  • Might be better not = to start groovysh, might be mentioned in Dockerfile comments instead
    • It's just a default to be run when the user does "docker= run", they can specify an alternative command to run if they choose (= see my grape example further down).=C2=A0 Ruby, JRuby, and Python all do th= is, and it's mentioned in Docker's best practices.
  • Add Dockerfile comme= nts, at least a link to the repo containing the dockerfiles
      • =
    • Did you mean a link to the Docker Hub page?=C2=A0 If not, what comments= do you think would be helpful in the Dockerfiles?
  • Add a LICENSE file to the github repo
    • Good catch.= =C2=A0 Done.
  • Add a travis job to the github r= epo that verifies the Dockerfiles
    • Yea, I intend to chang= e the readme to link to the Docker Hub page (once published) and a Travis j= ob, as you've suggested.=C2=A0 Build automation is something I have to = work out yet, goes with the templating work I mentioned.
  • Provide one sample image on top of those images with some h= ello world application
    • Usage is pretty straightforwa= rd, but I could do that.=C2=A0 It probably should be in a separate repo tho= ugh, don't you think?=C2=A0 Also any suggestions on a good sample?=C2= =A0 I was thinking something not compiled Groovy, because for that you'= d just run with Java Docker image, no need for Groovy on path.=C2=A0 Maybe = a script of some kind.
  • Check if grapes can be run from contain= ers
    • Grape seemed to work, was there a particular problem you we= re concerned about?
$ docke= r run -it --rm --name groovy groovy:jre8-latest
Dec 11, 2016 9:37:40 AM java.util.pr= efs.FileSystemPreferences$1 run
INFO: Created user preferences directory.
Groovy Shell (= 2.4.7, JVM: 1.8.0_111)
Type ':help' or ':h' for help.
-----------------------= -----------------------------------------------------------------= ----------------------------------------------------------------------------------------------------------------------
groovy:000> groov= y.grape.Grape.grab(group:'org.springframework', module:'sp= ring', version:'2.5.6')
=3D=3D=3D> null

$ docker r= un -it --rm --name groovy groovy:jre8-latest grape install 'org.springf= ramework' 'spring' '2.5.6'
:: loading settings :: url =3D jar:fi= le:/opt/groovy/lib/ivy-2.4.0.jar!/org/apache/ivy/core/settings/iv= ysettings.xml
:: resolving dependencies :: caller#all-caller;working72
<= /div>
=C2=A0 =C2=A0 =C2=A0 = =C2=A0 confs: [default]
=C2=A0 =C2=A0 =C2=A0 =C2=A0 found org.springframework#spring= ;2.5.6 in jcenter
=C2=A0 =C2=A0 =C2=A0 =C2=A0 found commons-logging#commons-log= ging;1.1.1 in jcenter
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 [SUCCESSFUL ] org.springframework#spring;2.5.6!spring.jar (2741ms)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 [SUCCESSFUL ] = commons-logging#commons-logging;1.1.1!commons-logging.jar (719ms)

On Sun, Dec 11, 2016 at 3:3= 2 AM, Thibault Kruse <tibokruse@googlemail.com> wrote= :
Some minor comments:
- might be better not to start groovysh, might be mentioned in
Dockerfile comments instead
- Add Dockerfile comments, at least a link to the repo containing the
dockerfiles
- Add a LICENSE file to the github repo
- Add a travis job to the github repo that verifies the Dockerfiles
- check if grapes can be run from containers
- Provide one sample image on top of those images with some hello
world application


On Sun, Dec 11, 2016 at 3:24 PM, Keegan Witt <keeganwitt@gmail.com> wrote:
> Sorry for the long turnaround on this.=C2=A0 I've got some basic D= ockerfiles put
> together: https://github.com/keeganwitt/groovy= -docker.=C2=A0 Please let me know
> what I can improve.=C2=A0 One thing I might do is template out the Doc= kerfiles
> similar to what Ruby did to make it easier to publish images when ther= e's a
> new Groovy version.
>
> I planned on creating both Alpine and non-Alpine images since that see= ms to
> be the current practice.=C2=A0 But we need to get GROOVY-7906 resolved= for the
> Alpine images to work.
>
> I'm concerned about whether it'd be legal for us to distribute= the Oracle
> JDK with Groovy.=C2=A0 I saw this article on the topic:
> http://blog.takipi.com/run= ning-java-on-docker-youre-breaking-the-law/.=C2=A0 I
> don't speak legalize though.=C2=A0 I haven't seen anyone else = (Jruby, etc)
> publishing Oracle JDK, and Oracle has never published Docker images th= at
> were not OpenJDK.=C2=A0 The only images floating out there have been > community-created.=C2=A0 So for the time being, I don't plan to pu= blish Oracle
> based images.
>
> Once we think these look good, I'll move the repo over to groovy o= rg in
> Github and we'll get them published to Docker Hub.=C2=A0 Maybe we = could also ask
> Apache Infra to get them added to https://hub.docker.com/u/apac= he/, I
> haven't decided.=C2=A0 What do you think?
>
> On Fri, Sep 9, 2016 at 11:19 PM, Corum, Michael <mcorum@rgare.com> wrote:
>>
>> Not related to Groovy as much.=C2=A0 We=E2=80=99ve never been able= to get OpenJDK (7 or
>> 8) to work properly with Oracle JDBC drivers on Alpine.=C2=A0 Alwa= ys have to use
>> Oracle JDK and in the research we did, we found others with the sa= me issues.
>>
>> Michael Corum
>>
>> VP, Technical Architecture Solutions
>>
>>
>>
>> RGA Reinsurance Company
>>
>> 16600 Swingley Ridge Road
>>
>> Chesterfield, Missouri 6301701706
>>
>> T 636.736.7066
>>
>> www.rgare.com
>>
>>
>>
>>
>> From: Guillaume Laforge <glaforge@gmail.com>
>> Reply-To: "users@groovy.apache.org" <users@groovy.apache.org>
>> Date: Friday, September 9, 2016 at 10:16 PM
>> To: "users@groovy.apache.org" <users@groovy.apache.org>
>> Subject: Re: Groovy Docker images
>>
>> Out of curiosity, what's the problem with OpenJDK?
>> Is it related to Groovy or not at all?
>>
>> On Sat, Sep 10, 2016 at 5:09 AM, Corum, Michael <mcorum@rgare.com> wrote:
>>>
>>>
>>> Either one
>>> Alpine =E2=80=93 I suspect others will want other options thou= gh
>>> Would most definitely prefer Oracle but I assume other would w= ant OpenJDK
>>> as well.=C2=A0 For my purposes OpenJDK just doesn=E2=80=99t wo= rk at all.
>>>
>>> Michael Corum
>>>
>>> VP, Technical Architecture Solutions
>>>
>>>
>>>
>>> RGA Reinsurance Company
>>>
>>> 16600 Swingley Ridge Road
>>>
>>> Chesterfield, Missouri 6301701706
>>>
>>> T 636.736.7066
>>>
>>> www.rgare.com
>>>
>>>
>>>
>>>
>>> From: Keegan Witt <keeganwitt@gmail.com>
>>> Reply-To: "users@groovy.apache.org" <users@groovy.apache.org>
>>> Date: Friday, September 9, 2016 at 9:48 PM
>>> To: "users@groovy.apache.org" <users@groovy.apache.org>
>>> Subject: Groovy Docker images
>>>
>>> I was thinking of putting together some Docker images for Groo= vy, with
>>> the idea they might be useful to base Grails, Gradle, etc imag= es on and
>>> wondered people's opinions on a few things.
>>>
>>> Should I install Groovy manually in somewhere like /opt?=C2=A0= Or use SDKMAN?
>>> Should I have images based on Alpine and Debian? Alpine only?<= br> >>> I presume OpenJDK images are fine as bases?=C2=A0 Any reason w= e'd need an
>>> Oracle based image too?
>>>
>>> Thoughts?
>>>
>>> -Keegan
>>
>>
>>
>>
>> --
>> Guillaume Laforge
>> Apache Groovy committer & PMC Vice-President
>> Developer Advocate @ Google Cloud Platform
>>
>> Blog: http://glaforge.appspot.com/
>> Social: @glaforge / Google+
>
>


--001a1149d3a4d1a611054378d6c5--