Re: Deployment Strategy: lifecycle hooks how to inject configuration

Another example of where this can be useful is where the primary process in the container doesn't do what is required of process ID 1. That is, reap zombie processes. If that becomes an issue you can use a run script wrapper like: #!/bin/sh trap 'kill -TERM $PID' TERM INT /usr/libexec/s2i/run

Re: Deployment Strategy: lifecycle hooks how to inject configuration

Badly worded perhaps. In some cases you don't have the ability to modify an existing image with the application in it, plus you may not want to create a new custom image as a layer on top. In those cases, if all you need to do is some minor tweaks to config prior to the application starting in

Re: Deployment Strategy: lifecycle hooks how to inject configuration

Hi Graham, This doesn't make sense to me: > 3. If don't want to create a new custom image. If you wanna run your application in a container you have to create a custom image with the application. There's no way around, because container images are immutable. You can only choose how you will

Re: Deployment Strategy: lifecycle hooks how to inject configuration

> On 22 Feb 2018, at 3:21 am, Fernando Lozano wrote: > > Hi Dan, > > As you learned, lifecycle hooks were not made to change anything inside a > container image. Remember that container images are, by design, immutable. It > looks you want to build a custom container

Re: How to use DNS hostname of OpenShift on AWS

Michael are you running OpenShift on AWS? https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/aws-ansible is the AWS reference architecture and it does use openshift-ansible once the infrastructure is built, but it uses a dynamic inventory. It’s not an

Re: Deployment Strategy: lifecycle hooks how to inject configuration

Hi Dan, As you learned, lifecycle hooks were not made to change anything inside a container image. Remember that container images are, by design, immutable. It looks you want to build a custom container image that includes your customizations to the wildfly configs plus your application. There

upgrading from Origin 3.6 to 3.6.1

Hi all, whats the recommended way to upgrade from Origin 3.6 to 3.6.1 ( rpm-based install)? There seems to be no upgrade playbook. I have set up a cluster when 3.6 was out, and adding new nodes *now* ( using openshift-ansible/playbooks/byo/openshift-node/scaleup.yml ) will install the 3.6.1

Re: Deployment Strategy: lifecycle hooks how to inject configuration

On Wed, 2018-02-21 at 14:43 +0200, Dan Pungă wrote: > Hello all! > > Trying to build an OShift configuration for running a Java app with a > Wildfly server. > I've setup this with ChainBuilds where the app's artifacts are > combined with a runtime image of Wildfly. > > For this particular app,

RE: How to use DNS hostname of OpenShift on AWS

Deploying with https://github.com/openshift/openshift-ansible you can define the hostnames in your inventory file. There is a sample inventory file at https://docs.openshift.org/latest/install_config/install/advanced_install.html that shows how to define the master/etcd/nodes, and those names

How to use DNS hostname of OpenShift on AWS

Hi, I'm trying to figure out how to use the DNS hostname when deploying OpenShift on AWS using https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/aws-ansible Currently it uses private dns name, eg, ip-10-2-7-121.ap-southeast-2.compute.internal but that isn't