Hmm yeah I don’t have strong feelings about how we should tag JDK versions, how do other projects do it?
On Sun, Aug 15, 2021 at 2:08 PM Mich Talebzadeh <mich.talebza...@gmail.com> wrote: > Thanks for the info. > > One thing we need to discuss is the convention for naming these > dockerfiles. I just created two spark version with java 11 and java 8 > > For example: > > REPOSITORY TAG IMAGE ID CREATED SIZE > spark 3.1.1_java8 f42d33ee0458 2 minutes ago 1.07GB > spark 3.1.1 c62b542764f6 2 hours ago 635MB > > > These are both based on Spark 3.1.1, one with Java 11 (latest on Debian > buster) and the other one with Java 8. The TAG is the identifier > > What conventions do we want to use with TAG above for clarity of pull? > > HTH > > > > view my Linkedin profile > <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> > > > > *Disclaimer:* Use it at your own risk. Any and all responsibility for any > loss, damage or destruction of data or any other property which may arise > from relying on this email's technical content is explicitly disclaimed. > The author will in no case be liable for any monetary damages arising from > such loss, damage or destruction. > > > > > On Sun, 15 Aug 2021 at 20:24, Holden Karau <hol...@pigscanfly.ca> wrote: > >> I don’t think we need a new repo for working on proposed Dockerfiles. You >> can take a look at the existing Dockerfiles, file a JIRA, and make a fork, >> then raise a PR (eg follow the usual development process). >> >> On Sun, Aug 15, 2021 at 9:51 AM Mich Talebzadeh < >> mich.talebza...@gmail.com> wrote: >> >>> >>> Maybe this one? >>> >>> >>> https://github.com/apache/spark/tree/master/resource-managers >>> >>> >>> >>> >>> >>> >>> view my Linkedin profile >>> <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> >>> >>> >>> >>> *Disclaimer:* Use it at your own risk. Any and all responsibility for >>> any loss, damage or destruction of data or any other property which may >>> arise from relying on this email's technical content is explicitly >>> disclaimed. The author will in no case be liable for any monetary damages >>> arising from such loss, damage or destruction. >>> >>> >>> >>> >>> On Sun, 15 Aug 2021 at 16:28, Mich Talebzadeh <mich.talebza...@gmail.com> >>> wrote: >>> >>>> Thanks, Sean got it. >>>> >>>> So who will create a new repository in this case. For example a new >>>> repository titled >>>> >>>> docker-and-kubernetes >>>> >>>> along those lines >>>> >>>> So I can pull it and start working on it in my local >>>> >>>> >>>> view my Linkedin profile >>>> <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> >>>> >>>> >>>> >>>> *Disclaimer:* Use it at your own risk. Any and all responsibility for >>>> any loss, damage or destruction of data or any other property which may >>>> arise from relying on this email's technical content is explicitly >>>> disclaimed. The author will in no case be liable for any monetary damages >>>> arising from such loss, damage or destruction. >>>> >>>> >>>> >>>> >>>> On Sun, 15 Aug 2021 at 16:23, Sean Owen <sro...@gmail.com> wrote: >>>> >>>>> No, we can't give write access to Apache repos of course, not to >>>>> anyone but committers. >>>>> People contribute by opening pull requests. >>>>> >>>>> >>>>> On Sun, Aug 15, 2021 at 10:11 AM Mich Talebzadeh < >>>>> mich.talebza...@gmail.com> wrote: >>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> >>>>>> With reference to recent threads/discussions on creating ready-made >>>>>> docker images for spark, spark-py and spark-R, it would be great to >>>>>> create >>>>>> a project/repository in Apache Spark GitHub specifically for this >>>>>> [orpose. >>>>>> >>>>>> >>>>>> Would some administrator of this https://github.com/apache/spark >>>>>> >>>>>> give my email mich.talebza...@gmail.com appropriate access to create >>>>>> the said repository or please let me know who I need to contact? >>>>>> >>>>>> >>>>>> Regards, >>>>>> >>>>>> >>>>>> Mich >>>>>> >>>>>> >>>>>> >>>>>> view my Linkedin profile >>>>>> <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> >>>>>> >>>>>> >>>>>> >>>>>> *Disclaimer:* Use it at your own risk. Any and all responsibility >>>>>> for any loss, damage or destruction of data or any other property which >>>>>> may >>>>>> arise from relying on this email's technical content is explicitly >>>>>> disclaimed. The author will in no case be liable for any monetary damages >>>>>> arising from such loss, damage or destruction. >>>>>> >>>>>> >>>>>> >>>>> -- >> Twitter: https://twitter.com/holdenkarau >> Books (Learning Spark, High Performance Spark, etc.): >> https://amzn.to/2MaRAG9 <https://amzn.to/2MaRAG9> >> YouTube Live Streams: https://www.youtube.com/user/holdenkarau >> > -- Twitter: https://twitter.com/holdenkarau Books (Learning Spark, High Performance Spark, etc.): https://amzn.to/2MaRAG9 <https://amzn.to/2MaRAG9> YouTube Live Streams: https://www.youtube.com/user/holdenkarau
