Bug 1498613
| Summary: | [RFE] Allow APB tooling to specify Dockerfile name when building | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Dylan Murray <dymurray> |
| Component: | Service Broker | Assignee: | Dylan Murray <dymurray> |
| Status: | CLOSED ERRATA | QA Contact: | Zhang Cheng <chezhang> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.7.0 | CC: | aos-bugs, wmeng |
| Target Milestone: | --- | ||
| Target Release: | 3.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-05 09:29:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dylan Murray
2017-10-04 18:56:36 UTC
Verified with latest apb tool.
Fixed.
Successfully installed Jinja2-2.9.6 MarkupSafe-1.0 PyYAML-3.12 apb-1.0.0 backports.ssl-match-hostname-3.5.0.1 cachetools-2.0.1 certifi-2017.7.27.1 chardet-3.0.4 dictdiffer-0.6.1 docker-2.5.1 docker-pycreds-0.2.1 google-auth-1.1.1 idna-2.6 ipaddress-1.0.18 kubernetes-3.0.0 openshift-0.3.2 pyasn1-0.3.7 pyasn1-modules-0.1.4 python-dateutil-2.6.1 python-string-utils-0.6.0 requests-2.18.4 rsa-3.4.2 ruamel.ordereddict-0.4.13 ruamel.yaml-0.15.34 six-1.11.0 urllib3-1.22 websocket-client-0.44.0
# apb build -h
usage: apb build [-h] [--tag TAG] [--registry REGISTRY] [--org ORG]
[--dockerfile DOCKERFILE]
optional arguments:
-h, --help show this help message and exit
--tag TAG Tag of APB to build
--registry REGISTRY Registry prefix of APB to prepend to tag
--org ORG, -o ORG Organization of APB to publish to
--dockerfile DOCKERFILE, -f DOCKERFILE
Name of Dockerfile to build with
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0636 |