That appears to have been fixed in 1.1.3 (the panic you hit). On Thu, Mar 3, 2016 at 3:29 PM, Candide Kemmler <candide@intrinsic.world> wrote: > oc v1.1.0.1-1-g2c6ff4b > kubernetes v1.1.0-origin-1107-g4c8e6f4 > > will do tomorrow > >> On 03 Mar 2016, at 22:28, Clayton Coleman <ccole...@redhat.com> wrote: >> >> What does "oc version" report? Can you file an issue for this? >> >> On Thu, Mar 3, 2016 at 3:28 PM, Clayton Coleman <ccole...@redhat.com> wrote: >>> In order to do a build you have to provide input. The input for a >>> build comes from Git, other images, but that's all we support today. >>> >>> On Thu, Mar 3, 2016 at 3:18 PM, Candide Kemmler <candide@intrinsic.world> >>> wrote: >>>> Hi Clayton, >>>> >>>> I tried: >>>> >>>> oc new-build openshift/jboss-webserver30-tomcat7-openshift >>>> https://github.com/fluxtream/fluxtream-admin-tools.git --strategy=docker -o >>>> yaml >>>> >>>> and got the following stack trace: >>>> >>>> https://gist.github.com/ckemmler/8ad03537eb39865c9fc3 >>>> >>>> Also, I'm confused as to the gitrepo parameter: my goal is to just add a >>>> file to an existing image; I shouldn't need to point to a git repo for >>>> that. >>>> >>>> Best >>>> >>>> On 03 Mar 2016, at 22:10, Clayton Coleman <ccole...@redhat.com> wrote: >>>> >>>> oc new-build BASEIMAGE GITREPO --strategy=docker -o yaml >>>> >>>> >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
