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

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-5372:
-------------------------------------

IMO, we should not invest any more time in "WildFly: docker" at all, for me just configuration issues makes me discouraged. For a developer, they need to go through a special setup to configure a data source, which is error prone will take a lot of our time to invest in good documents. Here I do not agree with the argument that it is a quick and easy way to test for non-developers. I feel it is not. Also, when we spin images we should keep the immutability at the core, we are asking for trouble later if we are not.

On "Throntail" and "SpringBoot", I would extend to both "Docker" and "OpenShift", as one build over another. Both of these are similar development paradigms like using maven, and environment and property files for configuration. If we have time, I would say we should spend on build tools like Gradle and Docker Compose for these to help wider developer audience.

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