Thank you Ben, I will try this out. On Tue, Jun 7, 2016 at 7:53 PM, Ben Parees <[email protected]> wrote:
> > > On Tue, Jun 7, 2016 at 9:07 AM, Rupali Behera <[email protected]> wrote: > >> Hi, >> >> I wanted to create an image using OC >> <https://github.com/openshift/origin/blob/master/docs/cli.md> command >> line tool to which I want to pass only the war file, like we can do using >> s2i <https://github.com/openshift/source-to-image> build with binary >> content. >> >> Is it possible using the OC >> <https://github.com/openshift/origin/blob/master/docs/cli.md> command >> line tool ? >> > > it's possible using binary builds: > > https://docs.openshift.org/latest/dev_guide/builds.html#binary-source > > you'll want to first define a binary type build using > oc new-build <someimage> --to <targetimagename> --binary > > then > oc start-build <yourbuildconfig> --from-file=your.war > > Note that today only the Wildfly images support a single file as the > input, the EAP and JWS images will be updated to support that model soon. > > In the meantime, you can instead create a directory structure of: > deployments/your.war > > and then pass --from-dir=. (where "." is the dir containing the > "deployments" directory) and that will work with wildfly, EAP, and JWS. > > > > > >> >> -- >> Thanks, >> Rupali >> >> _______________________________________________ >> dev mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> >> > > > -- > Ben Parees | OpenShift > > -- Thanks, Rupali
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
