[
https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-5372:
-------------------------------------
I agree that there is not much use in promoting the standalone WildFly based Docker image,
as it is not straightforward to configure data sources or any other configuration. Teiid
Thorntail implementation does ease the configuration issue.
There is Docker Maven Plugin, that can essentially build images based on the pom file. I
am not sure what JDK image it uses. The Fabric8 maven plugin extends the docker maven
plugin which can also help generate images for docker and OpenShift deployments.
BTW, for multiple VDBs to work we need to come up with a way to package multiple VDB
contents into a single archive and we can devise to deploy them into the engine.
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)