[teiid-issues] [JBoss JIRA] (TEIID-5372) Enhance docker support

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595722#comment-13595722 ] 

Steven Hawkins commented on TEIID-5372:
---------------------------------------

> I think what we need is to create a page summarizing possible teiid deployments (or maybe there's one?) including wildfly, wildfly with docker, thorntail and openshift

There isn't really a page focusing across the deployment models, but there is collateral on each in various locations.  

A quickstart page under http://teiid.io/teiid_four_ways/ would be good.

wildfly - is covered by the formal docs and there are https://github.com/teiid/teiid-quickstarts

wildfly with docker - other than the wiki that you mentioned, there isn't much on that.  We started done the path of emulating the other platforms docker usage https://github.com/shawkins/teiid-openshift-templates/tree/master/server-docker in the context of creating special purpose openshift images.  That effort was fully subsumed by the images generated by teiid-komodo.  For wildfly with docker to make sense we need to clarify the expected usage - something that is immutable, something ephemeral, or something persistently mutable.  Are you making the case in the previous comment for something mutable?

thorntail - has documentation and https://github.com/teiid/thorntail-teiid-examples which needs updated per TEIID-5382 as most show the older main method for launching Swarm.

thorntail with openshift - https://github.com/rareddy/teiid-openshift-demo/

> Enhance docker support
> ----------------------
>
>                 Key: TEIID-5372
>                 URL: https://issues.jboss.org/browse/TEIID-5372
>             Project: Teiid
>          Issue Type: Enhancement
>            Reporter: Rafal Korytkowski
>            Assignee: Rafal Korytkowski
>            Priority: Optional
>
> Currently there's limited support for docker in Teiid, which can be enabled by adding -Ddocker=true to the build command. The generated image is based on CentOS and running standalone on the Wildfly server. Latest builds are pushed to https://hub.docker.com/r/jboss/teiid/, but versions are not tagged automatically with releases. Development with Docker is not supported.
> Proposed changes:
> 1. Produce docker image based on Alpine, which is better suited for microservices, in addition to CentOS.
> 2. Automatically tag versions in Docker when doing releases.
> 3. Support development by providing a docker-compose file with the possibility to start server in a debug mode and enabled auto-redeployment of code changes.
> 4. Optionally provide a Docker image for building code using maven in Docker. Having Docker as the only prerequisite is convenient for CI environments and makes the build environment agnostic.
> [~shawkins], [~rareddy], thoughts?



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)