On 05/26/2016 02:38 AM, Matei Zaharia wrote: > Just wondering, what is the main use case for the Docker images -- to > develop apps locally or to deploy a cluster? I use docker images for both development and deploying on production cluster. As it makes sure I have the correct version of Java and Spark. If the image is really just > a script to download a certain package name from a mirror, it may be > okay to create an official one, though it does seem tricky to make it > properly use the right mirror. I don't think that's an issue, as you will publish a docker image which will already have spark baked from which ever mirror you choose. The mirror issue will be only when people want to build their own image from published Dockerfile, then they can change the mirror if they prefer.
Here is the link to current Spark Dockerfile (https://gist.github.com/gurvindersingh/8308d46995a58303b90e4bc2fc46e343) I use as base, then I can start master and worker from it as I like. - Gurvinder > > Matei > >> On May 25, 2016, at 6:05 PM, Luciano Resende <luckbr1...@gmail.com >> <mailto:luckbr1...@gmail.com>> wrote: >> >> >> >> On Wed, May 25, 2016 at 2:34 PM, Sean Owen <so...@cloudera.com >> <mailto:so...@cloudera.com>> wrote: >> >> I don't think the project would bless anything but the standard >> release artifacts since only those are voted on. People are free to >> maintain whatever they like and even share it, as long as it's clear >> it's not from the Apache project. >> >> >> +1 >> >> >> -- >> Luciano Resende >> http://twitter.com/lresende1975 >> http://lresende.blogspot.com/ > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
