[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=13599741#comment-13599741 ] 

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

> Sure, if you externalized the volume mount for configuration, that is the simplest route. Same could be said for modules.

It does not appear that anyone promotes a base wildfly image that is persistently mutable.  The usage scenarios that jboss/red hat promotes are an s2i base image (https://github.com/openshift-s2i/s2i-wildfly) and the simple base image (https://github.com/jboss-dockerfiles/wildfly).  So I'm going to side with Ramesh and say there isn't a lot of value in offering this approach on our own - even just as a developer aid as it should be just as easy for a developer to bring up a full wildfly or arquillian tests.

Option 1, we can keep building our own base image with the following updates:
- as Rafal suggests add a latest tag and provide some example(s) that demonstrate extending the image via a dockerfile using cli to configure the system.  Rather than our old example which 
- add some documentation to the dockerhub page 

Option 2, just remove the teiid community docker image and push updates to the jboss dockerfile for teiid - https://github.com/jboss-dockerfiles/teiid

> 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)