Run in order https://hub.docker.com/r/jboss/drools-workbench-showcase then https://hub.docker.com/r/jboss/kie-server-showcase/ and use the legacy API21 --link call https://docs.docker.com/engine/reference/commandline/network_connect/
JBOSS Drools Workbench GUI
Kie Server REST endpoint
We have at least two paths to bringing up a kie-server container - add the kie-server war to a clean Tomcat or JBoss docker image - or use the built in images on dockerhub around the JBoss JEE server.
The last stable 7.18.0.Final version (March 2019) of the kie-server https://docs.jboss.org/drools/release/7.18.0.Final/drools-docs/html_single/#_ch.kie.server is in use
Kie Server using the JBoss based image in DockerHub
Start with the image in https://hub.docker.com/r/jboss/kie-server
Kie Server on the Tomcat Image
Essentially we will be using a static CI/CD pipeline consisting of the following hybrid architecture (most services on AWS, some outside like github and an jenkins server).
All the following CI/CD pipeline steps can be done either using AWS Lambda triggers or encoded in an external jenkins job.
A DockerFile and associated configuration artifacts is checked into a git repo (github or CodeCommit).
On commit trigger - the deployment server (Jenkins or CodeBuild) pushes the repo contents to an S3 bucket for use by CodeBuild (this allows swapping out the git repo source)
AWS CodeBuild (same as Jenkins) project builds the docker image and pushes it to a image repository like nexus3, AWS ECR or DockerHub.
AWS CodeDeploy receives an ECS
Static Infrastructure - CloudFormation or Console based
Github Docker Source
AWS S3 Bucket for DockerFile source upload