* 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
Bug 1366475
Bugzilla link https://bugzilla.redhat.com/show_bug.cgi?id=1366475
Detailed explanation
an attempt to pull the builder image to obtain labels was made; the correct thing was
to pull the locally build image we were rebuilding
- update command line options descriptions to mention assemble-runtime
script
- move assemble-runtime script to the scripts sub-directory in the
resulting application image (run script is already here, so it looks
strange that they're in a different places)
- simplify code a bit (before we were extracting USER from the runtime
image and passing this user to the Docker during runtime container
creation. It looks useless, because we can just omit user and Docker
will use default USER for us)
From now you can create final image that is based on the image that is
different than builder image. To use it provide --runtime-image option
with image that will be used in runtime.
Also specify --runtime-artifact option (one or more times) with a list
of files and directories that will be copied into resulting image.
Alternatively this mapping can be extracted from the
io.openshift.s2i.assemble-input-files annotation on a runtime image.
To execute custom logic to arrange image to a desired state, you can
leverage "assemble-runtime" script. You can 1) put it .s2i/bin directory
with application sources 2) download it from remote location (-s option)
or 3) have it inside a runtime image (but don't forget to add
io.openshift.s2i.scripts-url label on it).
Instead of leaving the name blank and letting the Docker daemon name
containers with random strings like 'lonely_thompson', we give proper
names so that we can identify and filter containers created by S2I
later.
Names take a fixed prefix, 's2i_', and a random suffix. The builder
image is also used to compose the container name, replacing with
underscores characters that would be invalid for a container name.
Example:
$ s2i build \
git://github.com/openshift/ruby-hello-world \
centos/ruby-22-centos7 \
hello-world-app
The above creates a temporary container named
's2i_centos_ruby_22_centos7_397cfecd'.
- 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.
- Bootstrap.process(): don't try to do chmod on Windows
- cmd/s2i/main.go: fix file descriptors leak
- GenerateConfigFromLabels: remove unused parameter
- GenerateConfigFromLabels: use local variable for a list of labels
- sti.New(): rename argument from req to config
- DefaultCleaner: don't inherit ~30 methods while we're using just two
- STI.Prepare(): simplify
- DockerIgnorer.getListOfFilesToIgnore(): pass string instead of api.Config
- util.FixInjectionsWithRelativePath: rewrite to not modify its argument
Go prints a stack trace of all goroutines by default on SIGQUIT, except
those related to the runtime. To include all goroutines, set
GOTRACEBACK=2 or GOTRACEBACK=crash.
This custom handler was suppressing Go's default behavior.
