Hide Forgot
Description of problem: oc new-build --binary <some s2i imagestream> should create a source type build(because the image is a builder), but it creates a docker type build instead. you can't specify --strategy because that requires you also specify source, and you can't specify source with a binary build. oc new-build --binary should create a docker or s2i type build as appropriate based on the image type (since it can't check the repo like it normally would)
(In reply to Ben Parees from comment #0) > Description of problem: > > oc new-build --binary <some s2i imagestream> should create a source type > build(because the image is a builder), but it creates a docker type build > instead. > > you can't specify --strategy because that requires you also specify source, > and you can't specify source with a binary build. > > > oc new-build --binary should create a docker or s2i type build as > appropriate based on the image type (since it can't check the repo like it > normally would) Does this mean if the image is a builder image will create a s2i build type,and for normal image, will create a docker build type ?
> Does this mean if the image is a builder image will create a s2i build type,and > for normal image, will create a docker build type ? by default yes (though we may only detect that for imagestreams. detecting it for raw docker images is harder), but regardless the user should also be able to override the behavior with --strategy
Fixed with https://github.com/openshift/origin/pull/7702
verified against origin,update the status to modified. steps: #oc new-build --binary ruby #oc new-build --binary registry.access.redhat.com/rhscl/ruby-22-rhel7:latest -n haowang --to=haowang/ruby22test #oc new-build --binary registry.access.redhat.com/rhscl/ruby-22-rhel7:latest -n haowang --to=haowang/ruby22test1 --strategy=docker [root@ip-172-18-8-159 origin]# oc get bc NAME TYPE FROM LATEST ruby Source Binary 0 ruby22test Source Binary 0 ruby22test1 Docker Binary 0
As bug is against the origin ,mark verified.