(sorry I said EAP a few times in there, I realize you're using the JWS image at the moment. doesn't change the response though)
On Thu, Mar 3, 2016 at 9:34 AM, Ben Parees <[email protected]> wrote: > > > On Thu, Mar 3, 2016 at 9:20 AM, Candide Kemmler <[email protected]> > wrote: > >> Mainly I have a multi-gb file that needs to be available to my webapp. >> Copying it over with each build is a lot of unnecessary bandwidth use and >> considerably slows down the process. Other binaries include a custom >> datastore <https://github.com/BodyTrack/datastore>. >> >> > you could certainly add a layer to the EAP image that includes this > binary file. You can do that using a docker-type build in openshift, which > will (by default) push the resulting image to the openshift registry. Then > you can reference your customized EAP builder image from the openshift > registry, thus avoiding the redistribution question. > > > > >> I'm suddenly nervous that deploying our code with the provided xPaas >> images would/is subject to a license agreement (and we have none so far). >> My assumption was that since it comes with Openshift Origin it would be >> free to use just like the platform it runs on... >> > > If you prefer to avoid this issue (which is still evolving), you can use > our wildfly image instead: > > https://github.com/openshift/sti-wildfly/ > > > > >> >> On 03 Mar 2016, at 15:13, Kevin Conner <[email protected]> wrote: >> >> >> On 2 Mar 2016, at 09:53, Ben Parees <[email protected]> wrote: >> >> Is there a central place where Dockerfile for those images can be found, >> or alternatively are these images available to serve as a base image to >> start off from? >> >> It is unclear to me where Openshift Origin is fetching the containers >> from (e.g. jboss-webserver30-tomcat7-openshift) and if it is possible to >> fetch them from that same source to expand on them and push them to e.g. >> docker.io. >> >> >> We do not yet publish the source for these images since they contain >> information related to our build environment but this is something we are >> working on addressing. You shouldn’t need the docker source to achieve >> what you are after, everything would be in the image that you download from >> the registry. We already support the addition on various binaries through >> the S2I process, can I ask what binaries you are wanting to include and why >> you prefer to create your own image? >> >> As for the ability to push the images to dockerhub I would imagine that >> would be covered by any licensing agreement you have with us and >> redistribution may not be allowed. I’m not a lawyer so cannot provide a >> definitive answer, I would suggest you raise this question through the >> support channels so that they can provide you with an official, documented >> response. >> >> Kev >> >> -- >> JBoss by Red Hat >> >> >> > > > -- > Ben Parees | OpenShift > > -- Ben Parees | OpenShift
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
