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 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 wrote:
>>
>> What does "oc version" report?
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 wrote:
>
> What does "oc version" report? Can you file an issue for this?
>
> On Thu, Mar 3, 2016 at 3:28 PM, Clayton Coleman wrote:
>> In order to do a build you have t
What does "oc version" report? Can you file an issue for this?
On Thu, Mar 3, 2016 at 3:28 PM, Clayton Coleman 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, Ca
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 wrote:
> Hi Clayton,
>
> I tried:
>
> oc new-build openshift/jboss-webserver30-tomcat7-openshift
> https://github
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 parame
oc new-build BASEIMAGE GITREPO --strategy=docker -o yaml
will give you an example of the YAML / JSON used.
On Thu, Mar 3, 2016 at 2:47 PM, Candide Kemmler wrote:
> I'm hitting a wall with a simple docker build. Are there example of such
> builds online?
>
> I'm looking for some simple Build
I'm hitting a wall with a simple docker build. Are there example of such builds
online?
I'm looking for some simple BuildConfig that would take e.g. one of the
provided xPaas images and modify it to push it on the local registry.
___
users mailing lis
