Option to create a base image from a local BE installation (similar to BW) to use that image and just add CDD and ear file to build the application image.

[umueller-de]

Context
Option to create a base image from a local BE installation similar to a BWCE container and scripts/dockerfiles to add ear and CDD file to build the application image from base image (without using "Source-to-Image (S2I) toolkit")
Add the scripts and the dockerfile required to add the CDD and ear file.

e.g.,
Script:

CDD=IgniteClusterDeploy.cdd
EAR=fdcache.ear
ARG_APP_LOCATION=./appFiles
ARG_FROM_IMAGE=fd:be622
ARG_IMAGE_VERSION=fd:be622

ARG_CDD_FILE=$CDD

ARG_EAR_FILE=$EAR
ARG_DOCKER_FILE=DockerfileUpdateFromExistingImage

docker build --force-rm -f $ARG_DOCKER_FILE --build-arg ARG_APP_LOCATION="$ARG_APP_LOCATION" --build-arg ARG_FROM_IMAGE="$ARG_FROM_IMAGE" --build-arg ARG_CDD_FILE="$ARG_CDD_FILE" --build-arg ARG_EAR_FILE="$ARG_EAR_FILE" -t "$ARG_IMAGE_VERSION" .

Dockerfile: DockerfileUpdateFromExistingImage

ARG ARG_FROM_IMAGE
FROM $ARG_FROM_IMAGE as intermediate

ARG ARG_CDD_FILE
ARG ARG_EAR_FILE

COPY ./appFiles/$ARG_CDD_FILE /opt/tibco/be/application
COPY ./appFiles/$ARG_EAR_FILE /opt/tibco/be/application

ENV CDD_FILE=/opt/tibco/be/application/$ARG_CDD_FILE 
ENV EAR_FILE=/opt/tibco/be/application/$ARG_EAR_FILE

[rameshpolishetti]

hi @umueller-de we already supports this using s2i framework. Refer to the documentation - https://github.com/TIBCOSoftware/be-tools/wiki/Building-TIBCO-BusinessEvents-Application#method-two---building-using-source-to-image-s2i-toolkit

User can create BE base image using the option "s2ibuilder" once and then create BE application image by supplying base image + cdd/ear.

[rameshpolishetti]

As per the discussion with @umueller-de, I understand that user doesn't prefer to use s2i.
I remember that we have added this feature based on s2i framework as per some customer request. Lets have discussion with Vikram on this.

CC: @vpatil-tibco

[vpatil-tibco]

@umueller-de Earlier we use to do a 2 step image creation in BE 5.5/5.6 times. But we got a feedback, from customers and field that there is no reason to do a 2 step process they would anyway be doing base+application. So then we changed that to do a one step single image i.e. base+app.
So is there a specific usecase they are targeting where base image gets used differently? At the end of the day they will still have to do base+app image.