Red Hat Bugzilla – Bug 1289015
[devexp_public_707]No place to input pushSecret info when try to push result image to docker hub via oc new-build --to-docker
Last modified: 2016-01-20 10:26:56 EST
Description of problem:
If try to push result image to docker with command oc new-build --to-docker, there is no place to input secret info which causes build push fails:
Failed to push image: unauthorized: access to the requested resource is not authorized
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. oc new-build -D $'FROM centos:7\nRUN yum install -y httpd' --to wzheng/myapp --to-docker=true
2. Check build log
Removing intermediate container 7097bf9322ce
Successfully built dfeefcc8f18a
I1207 08:41:22.472566 1 docker.go:86] Pushing image wzheng/myapp ...
F1207 08:41:27.707971 1 builder.go:59] Build error: Failed to push image: unauthorized: access to the requested resource is not authorized
Build failed for cannot being pushed.
There should be a place to input pushSecret.
@wzheng, we'll need to add a new option to `oc new-build` to allow passing the push secret. Will give you an update when the new option is merged.
reducing severity, user can edit the BC after creation to add a secret ref for now.
Rodolfo can you please make sure we have (or create) a card for this and then close this bug? Thanks.
(that is the process we follow for RFEs that are not customer initiated)
I found no relevant card, therefore created a new one to track the implementation of the new feature:
Closing this bug.