During the s2i build process not just the labels of the output Docker image are not created correctly under OpenShift 4.x, but also the command field. A workaround is shared here for this faulty behavior.
A new section is added to new_labels.md on a bug in OpenShift 4.x. The method of updating output image labels during the s2i build process is not possible currently in OpenShift 4.x and a corresponding workaround is described.
documentation of assemble-runtime-user's flag
add LABEL assemble-runtime-user
removing debug messages
change the failure reason of GetAssembleRuntimeUser
assemble-runtime-user is optional
generate completitions
check getAssembleRuntimeUser error
Add support for assemble-user label
Add support for assemble-user label
Add support for assemble-user label
Add support for assemble-user label
Add support for assemble-user label
* Prefer using https:// instead of git://
Both protocols are "smart" and should have similar performance.
HTTPS is encrypted, while the Git transport is plaintext.
HTTPS verifies the certificate of the server.
* Clean up comment
- "the source" means "s"
- no need to enumerate protocols
The pushd and popd commands in the example for save-artifacts example emit output to standard out. This will corrupt the tar stream, and prevent the reuse of the saved artifacts.
- s/Golang/Go/
- Make similar paragraphs similar, include the same list of languages.
The paragraph in docs/runtime_image.md contains more detailed
information.
- Spurious whitespace changes.
- sti -> s2i
- fix a couple of typos
- remove useless fmt.Sprintf() usage
- use api.Assemble constant
- UploadToContainer: rename argument
- docs/cli.md: correct the number of log levels
- docs/debugging-s2i.md: fix a typo
- don't use deprecated image: openshift/wildfly-8-centos -> openshift/wildfly-100-centos7
- update docs to use --pull-policy instead of deprecated --force-pull.
- replace .stifile by .s2ifile in --use-config option description.
